Monitoring: clean up PR #2484 and keep it as the app-telemetry draft

Abierto
#2,663 2 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 3 días

@AriyosenaS ya está trabajando en esto.

Desde el 7/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

deployment Infrastructure type: enhancement :gear:

Part of #2412. Can start right away.

Why

PR #2484 is a good prototype of the full telemetry chain (OpenTelemetry Collector, Prometheus, Jaeger, Grafana), but it is not the first step on the server: production runs Apache + mod_wsgi, where opentelemetry-instrument has no process to wrap. The first monitoring version runs next to the app instead (see the other sub-issues of #2412). This PR stays as a draft for the later application-telemetry step, and needs a clean-up first so it does no harm while it waits.

Tasks

Both #2484 and #2402

  • Restore script/import_oep_tables_to_local.py (both PRs delete it in the commit "update log filtering script").
  • Restore the scripts/ line in .gitignore and remove the script/import_oep_tables_to_local_test.py line. For personal ignores use .git/info/exclude.
  • Merge develop in (both PRs are conflicting).

#2484 only

  • Commit docker/otel-config.yaml. The compose file mounts it, but it is not in the branch, so the collector cannot start from a clean checkout.
  • Remove the log filter commits from this PR. The script moves into the usage-figures issue (sub-issue of #2412).
  • Move the four opentelemetry-* packages out of requirements.txt into a new pinned requirements-telemetry.txt. Every line in requirements.txt is pinned and that file goes into the production image.
  • Pin every image. Replace jaegertracing/all-in-one:latest (Jaeger v1, end of life since 2025-12-31) with cr.jaegertracing.io/jaegertracing/jaeger:<2.x>.
  • Make docker-compose-telemetry.yaml an override of docker/docker-compose.dev.yaml that only adds the telemetry services and changes the web command/environment, instead of a full copy of the dev stack.
  • Add --noreload to the instrumented runserver (the autoreloader runs the app in a child process).
  • Bind published ports to 127.0.0.1, and take the Grafana password from the environment instead of admin/admin.
  • Get pre-commit.ci green.
  • Convert the PR to draft and add one sentence to the description: not for production yet, because mod_wsgi needs the SDK set up in oeplatform/wsgi.py.

Done when

  • The diff of each PR against develop contains only its own files.
  • On a clean checkout, docker compose -f docker/docker-compose.dev.yaml -f docker/docker-compose-telemetry.yaml up starts all services including the collector.
  • #2484 is a draft with pre-commit.ci green.
Lenguaje dominante
Python
Estrellas
65
Forks
28
Merge medio
4 d 7 h
PR fusionados (30 d)
25

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenEnergyPlatform/oeplatform

Todos los issues de OpenEnergyPlatform/oeplatform

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.