3 ms·

For the tracing part of Otel, neither Prometheus nor Grafana are capable of doing that. Tracing is the most mature part of Otel and the most compelling use case

For the tracing part of Otel, neither Prometheus nor Grafana are capable of doing that. Tracing is the most mature part of Otel and the most compelling use case for it. For metrics, we've stayed with Prometheus and AWS Cloudwatch Metrics. The metrics part feels very under developed at the moment.

hinkley 2y ago
When I last looked 9 months ago, there were libraries of the metrics side of the tree still marked as experimental, that you couldn’t successfully send metrics without using. And a huge memory leak in the JS implementation that was only fixed 15 months ago: https://github.com/open-telemetry/opentelemetry-js/issues/4115 https://github.com/open-telemetry/opentelemetry-js/issues/41... Things, especially crosscutting concerns, you want to use in production should have stopped experiencing basic growing pains like this long before you touch them. It’s not baked yet. Come back in a year. Or two.
- barake 2y ago
  Everything is either in development or stable. There aren't statuses like alpha, beta, release candidate, etc. except for individual library releases. Metric clients will be marked as "development" until it goes "stable" [0]. Consequently it can be hard to determine the actual maturity level of any given implementation. Tracing is very mature, with metric and logging implementations stable for a number of popular languages [1]. the "experimental" status was renamed "development" [0] https://opentelemetry.io/docs/specs/otel/versioning-and-stability/#signal-lifecycle https://opentelemetry.io/docs/specs/otel/versioning-and-stab... [1] https://opentelemetry.io/docs/languages/#status-and-releases https://opentelemetry.io/docs/languages/#status-and-releases
  - hinkley 2y ago
    > the "experimental" status was renamed "development That doesn’t really change things now does it. It’s still a bunch of people sitting around saying “MMMM” loudly while eating half-raw cookies.

hinkley 2y ago

When I last looked 9 months ago, there were libraries of the metrics side of the tree still marked as experimental, that you couldn’t successfully send metrics without using. And a huge memory leak in the JS implementation that was only fixed 15 months ago: https://github.com/open-telemetry/opentelemetry-js/issues/4115 https://github.com/open-telemetry/opentelemetry-js/issues/41... Things, especially crosscutting concerns, you want to use in production should have stopped experiencing basic growing pains like this long before you touch them. It’s not baked yet. Come back in a year. Or two.

barake 2y ago
Everything is either in development or stable. There aren't statuses like alpha, beta, release candidate, etc. except for individual library releases. Metric clients will be marked as "development" until it goes "stable" [0]. Consequently it can be hard to determine the actual maturity level of any given implementation. Tracing is very mature, with metric and logging implementations stable for a number of popular languages [1]. the "experimental" status was renamed "development" [0] https://opentelemetry.io/docs/specs/otel/versioning-and-stability/#signal-lifecycle https://opentelemetry.io/docs/specs/otel/versioning-and-stab... [1] https://opentelemetry.io/docs/languages/#status-and-releases https://opentelemetry.io/docs/languages/#status-and-releases
- hinkley 2y ago
  > the "experimental" status was renamed "development That doesn’t really change things now does it. It’s still a bunch of people sitting around saying “MMMM” loudly while eating half-raw cookies.