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

[APM] Discuss: Configure columns in the Logstream component used in the Trace detail view #85947

Open
formgeist opened this issue Dec 15, 2020 · 3 comments
Labels
apm:logs discuss enhancement New value added to drive a business result Team:APM All issues that need APM UI Team support

Comments

@formgeist
Copy link
Contributor

Summary

Since #85859 we now have a Logstream component in the Trace detail view which fetches the logs relevant for the trace, we could opt to configure columns that are relevant for APM related traces.

We intended in the design to have the service.name show up as an indication based on the same legend from the Waterfall visualization. We could consider simply writing out the service.name but not sure if that's actually supported by the agents at the moment.

Do we prefer this column layout which would supersede the default/custom layout that the user has set up in Logs UI?

  • @timestamp
  • service.name ?
  • log.level ?
  • log.message

image

@formgeist formgeist added Team:APM All issues that need APM UI Team support enhancement New value added to drive a business result labels Dec 15, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui (Team:apm)

@formgeist formgeist changed the title [APM] Configure columns in the Logstream component used in the Trace detail view [APM] Discuss: Configure columns in the Logstream component used in the Trace detail view Dec 15, 2020
@formgeist
Copy link
Contributor Author

cc @cyrille-leclerc @nehaduggal @alex-fedotyev for your consideration

@botelastic
Copy link

botelastic bot commented Nov 1, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the stale Used to mark issues that were closed for being stale label Nov 1, 2021
@stale stale bot removed the stale Used to mark issues that were closed for being stale label Jul 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apm:logs discuss enhancement New value added to drive a business result Team:APM All issues that need APM UI Team support
Projects
None yet
Development

No branches or pull requests

3 participants