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

Separate telemetry by component #687

Open
Mirko-von-Leipzig opened this issue Feb 12, 2025 · 0 comments
Open

Separate telemetry by component #687

Mirko-von-Leipzig opened this issue Feb 12, 2025 · 0 comments
Labels
telemetry Relates to tracing and open-telemetry

Comments

@Mirko-von-Leipzig
Copy link
Contributor

Open-telemetry has service.name and service.namespace. Currently these are miden-node and empty respectively.

The specification indicates that service.name should be identical across horizontal scaling. Or in other words, we should probably have separate service.name for each component in the node i.e. store, rpc, block-producer. And then the namespace could simply be miden or miden-node.

Its unclear how easy this would be to implement, but it will require separately instrumenting each component somehow.

@Mirko-von-Leipzig Mirko-von-Leipzig added the telemetry Relates to tracing and open-telemetry label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
telemetry Relates to tracing and open-telemetry
Projects
None yet
Development

No branches or pull requests

1 participant