We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
Not sure where to add it but a logstash_id field would be a good idea.
It would allow customers to identify which logstash server redirected the logs.
This helps with debugging and operational issues.
It could be an object like
logstash.id logstash.name logstash.location logstash.hostname logstash.pipeline_id
Thanks,
Matthew
The text was updated successfully, but these errors were encountered:
+1 this. I have a step in my pipeline to add "ls_node" to capture the current Logstash node name for debugging.
Sorry, something went wrong.
We created meta-issue #940 to discuss capturing pipeline details in ECS. Closing in favor of the meta issue.
No branches or pull requests
Hi,
Not sure where to add it but a logstash_id field would be a good idea.
It would allow customers to identify which logstash server redirected the logs.
This helps with debugging and operational issues.
It could be an object like
logstash.id
logstash.name
logstash.location
logstash.hostname
logstash.pipeline_id
Thanks,
Matthew
The text was updated successfully, but these errors were encountered: