3 ms·
In the Elixir library, we don't even have metrics. I went into the OTel rabbit hole for two days trying to understand how is it better to Prometheus, just to le
by sph 3y ago
In the Elixir library, we don't even have metrics. I went into the OTel rabbit hole for two days trying to understand how is it better to Prometheus, just to learn it doesn't even do the basic thing, just traces.
I've mentally decided to just go Prometheus and ignore OpenTelemetry for the foreseeable future.
It's one of those things big players are hyping to preemptively lock you in their solution, but it's actually just alpha-quality new tech and "boring" "old" tech like Prometheus or statsd are simply more functional and better supported in the wild.
- filmor 3y agoMetrics are implemented in the `opentelemetry_experimental` application. Last time I tried them, they were still a bit buggy but working (not complete, thiugh).
- notpublic 3y agoElixir opentelemetry works quite well with Tempo. Tempo does the metric generation [1] and writes it to Prometheus. Tempo also does Service Graphs which works great with context propagation [2]. Btw, metric generation is not enabled in Tempo by default. # tempo.yml overrides: defaults: metrics_generator: processors: [service-graphs, span-metrics] # Prometheus --web.enable-remote-write-receiver # Grafana.yml [feature_toggles] enable = tempoSearch tempoBackendSearch traceToMetrics [1] https://grafana.com/docs/tempo/latest/metrics-generator/ https://grafana.com/docs/tempo/latest/metrics-generator/ [2] https://hexdocs.pm/opentelemetry_process_propagator/OpentelemetryProcessPropagator.html https://hexdocs.pm/opentelemetry_process_propagator/Opentele...