-
Notifications
You must be signed in to change notification settings - Fork 23
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
Support emitting map as an OpenTelemetry metric #140
Comments
im trying to get this service-map into my tracing pipeline. Anyone got any good idea on how to send the servicemap as traces? Can it be converted somehow? I thought service-maps were supposed to be sent via traces? |
The data here doesn't match 1:1 with traces, since they don't represent individual connections or requests, but rather the presence of any connection within a given time period. See the configuration flags for the Helm chart for enabling this feature: https://docs.otterize.com/reference/network-mapper/helm-chart#opentelemetry-exporter-parameters |
@orishoshan Ok! Thank you for your reply! One last question: are the metrics the same format as the ones produced by the ServiceGraphConnector ? |
Several different monitoring and observability solutions (like Grafana tempo) can natively visualize maps from timeseries data that follows a specific format.
If network mapper emits a OpenTelemetry timeseries with
from
andto
edges, the connections inferred from network-mapper can be easily visualized and used in external tools for performance, inventory, and observability use-cases.The text was updated successfully, but these errors were encountered: