Implement observability signals using OTEL #10

New issue

Open

opened 2025-10-08 00:37:47 -03:00 by dunossauro · 2 comments

dunossauro commented

2025-10-08 00:37:47 -03:00

Member

In @gutocarvalho 's notes, we have references to important observability signals like metrics, traces, and profiling. I think it would be a good idea to use OTEL (OpenTelemetry) for this, as it allows us to easily enable and disable observability signals using environment variables. Additionally, since we're using FastAPI, it already has the necessary contributions to both receive and send these signals.

We need to investigate if it's possible to deploy an OTEL collector in the infrastructure to redirect these signals appropriately. In the development environment, we can use the otel-lgtm image, which provides all the necessary services and is easy to test to ensure everything is being sent as expected.

In @gutocarvalho 's [notes](https://notes.bolha.tools/zukjODRTREWVBIca9d2vAQ#2-Observabilidade), we have references to important observability signals like metrics, traces, and profiling. I think it would be a good idea to use **OTEL (OpenTelemetry)** for this, as it allows us to easily enable and disable observability signals using environment variables. Additionally, since we're using **FastAPI**, it already has the necessary contributions to both receive and send these signals. We need to investigate if it's possible to deploy an OTEL collector in the infrastructure to redirect these signals appropriately. In the development environment, we can use the [**otel-lgtm**](https://github.com/grafana/docker-otel-lgtm) image, which provides all the necessary services and is easy to test to ensure everything is being sent as expected.

thiagojedi commented

2025-10-08 03:33:25 -03:00

Owner

Just to add to this, one of the reasons for using Deno in the frontend project is the OTEL integration ( see https://docs.deno.com/runtime/fundamentals/open_telemetry/ ).

So I agree on having an OTEL colector.

Just to add to this, one of the reasons for using Deno in the frontend project is the OTEL integration ( see https://docs.deno.com/runtime/fundamentals/open_telemetry/ ). So I agree on having an OTEL colector.