-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add field: process.thread.name #507
Comments
In our own implementation we're already using |
@cpmoore I'm interested in your setup: are you logging as JSON or parsing plain-text log files with logstash/filebeat/ingest node? |
@felixbarny We’re using filebeat to send plain text logs to logstash and parsing them with a grok filter. |
Yes, adding this field makes sense and is straightforward. I'm adding it to my (long) list of quick fixes. Of course if someone has the time to send over a PR for this, I can fast track the approval :-) |
I believe I opened the PR correctly. Still kinda a newbie 😄 |
@cpmoore You did, and were successful on the first try (no missing Thank you! 💯 |
There is already
process.thread.id
, however, a thread name is arguably more descriptive. The use case for this would be Java logging, for example. For this use case, it's useful to see in which thread a log has been emitted.The text was updated successfully, but these errors were encountered: