opentelemetry-erlang

You can use Uptrace to monitor routes/queries performance, errors, and partially logs (only Go at the moment and it is unofficial). Distributed tracing excels at finding the root cause and resolving issues in production. That is the future / present of any kind of monitoring and the potential is immense. >Also, are there plans for an Elixir client? Uptrace client is a just pre-configured distribution of OpenTelemetry so you try to configure OpenTelemetry https://github.com/open-telemetry/opentelemetry-erlang . We will provide a pre-configured client for Elixir if there is an interest.

> Elixir would create a telemetry Erlang `telemetry` is something different from OpenTelemetry. > Phoenix (and other libraries like Ecto, etc.) would use it And this is a fact. Both Plug, Phoenix, and Ecto are using Erlang's Telemetry library. > And the end goal was to have a Phoenix web UI that would come out of the box that you could goto and see a bunch of really useful things about your server's health This will probably be implemented as an external library in form of OpenTelemetry as I said. > Did all of that get scratched for OpenTelemetry? No, OpenTelemetry and Erlang's Telemetry have different goals. Erlang's Telemetry is meant to be lightweight metrics logging library with API for defining exposed metrics. OpenTelemetry is the OTP application that will ingest these metrics and will expose them to the external services like DataD