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
We often run in situations where the collector is meant to send data to a remote endpoint, and we run in networking issues.
We end up running traceroute to understand the problem.
I think instead having a traceroute receiver showing a trace with each span being a hop would be a valuable outcome.
receivers: traceroute: endpoint: example.com
traces
atoulme
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The purpose and use-cases of the new component
We often run in situations where the collector is meant to send data to a remote endpoint, and we run in networking issues.
We end up running traceroute to understand the problem.
I think instead having a traceroute receiver showing a trace with each span being a hop would be a valuable outcome.
Example configuration for the component
receivers:
traceroute:
endpoint: example.com
Telemetry data types supported
traces
Code Owner(s)
atoulme
Sponsor (optional)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: