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
Add trace to logs functionality for OS to allow OS users jump into their logs from tempo traces.
Currently, OS is not supported in trace to logs functionality. We want to add logic so OS is supported for this feature.
Implementation
This should be implemented after ES implementation.
This is hardcoded for splunk + loki here https://github.com/grafana/grafana/blob/2970c6db375e258a6fbf129c21b7210af248d40c/public/app/features/explore/TraceView/createSpanLink.tsx#L115 It just needs a case for elastic so it creates correct query.
And then in public/app/core/components/TraceToLogs/TraceToLogsSettings.tsx elasticsearch should be added.
public/app/core/components/TraceToLogs/TraceToLogsSettings.tsx
Discussed in grafana/grafana#51746
The text was updated successfully, but these errors were encountered:
gabor
Successfully merging a pull request may close this issue.
Summary
Add trace to logs functionality for OS to allow OS users jump into their logs from tempo traces.
Problem statement
Currently, OS is not supported in trace to logs functionality. We want to add logic so OS is supported for this feature.
Scope
Implementation
Solution
This should be implemented after ES implementation.
This is hardcoded for splunk + loki here https://github.com/grafana/grafana/blob/2970c6db375e258a6fbf129c21b7210af248d40c/public/app/features/explore/TraceView/createSpanLink.tsx#L115
It just needs a case for elastic so it creates correct query.
And then in
public/app/core/components/TraceToLogs/TraceToLogsSettings.tsx
elasticsearch should be added.Resources
Discussed in grafana/grafana#51746
The text was updated successfully, but these errors were encountered: