-
Notifications
You must be signed in to change notification settings - Fork 114
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
Revisit MP Metrics #296
Comments
From a distance, the observability situation seems to be disjointed. It seems to me the best choice long term may be to just standardize on OpenTelemetry APIs across the board. Or come up with MP APIs as facades, but right now we have both. |
@kito99 we don't have both as OpenTelemetry Metrics has not been adopted by MicroProfile as yet. The plan is to either adopt OpenTelemetry Metrics APIs or making MP APIs as facades, which heads towards that way already. |
@Emily-Jiang yes, I know. I guess what I'm saying is that it's strange that MP Metrics has its own API but MP Telemetry doesn't. Seems like they both should either have their own API or use OpenTelemetry. |
@kito99 good obeservation! The MP Telemetry uses the OpenTelemetry apis as OpenTelemetry under CNCF is a specification already. I think as for the metrics part, we can discuss further regarding our own Metrics API or adopt OpenTelemetry Metrics APIs. |
👍🏾 |
OpenTelemetry Metrics semantic convention is not stable as yet. |
We need to revisit MP Metrics included in MicroProfile 6.0. MP Metrics should work closely with MP Telemetry team together with MP Fault Tolerance to evaluate the urgency to align with OTel Metrics.
#292
The text was updated successfully, but these errors were encountered: