Skip to content
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

Include tracing information in the log records #102699

Closed
mshustov opened this issue Jun 21, 2021 · 1 comment · Fixed by #112973
Closed

Include tracing information in the log records #102699

mshustov opened this issue Jun 21, 2021 · 1 comment · Fixed by #112973
Assignees
Labels
Feature:Logging impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@mshustov
Copy link
Contributor

To implement log correlation, Kibana must include tracing information into the log records.
ECS schema contains tracing fields reserved for these needs. It means that Kibana should include the tracing fields when emits in the JSON layout.
We need to align with the Elasticsearch team on whether we should include trace identifiers in the logs with pattern layout, whether emitting should be configurable.

@mshustov mshustov added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Jun 21, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Logging impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants