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

Aperta
#2,663 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

@AriyosenaS ci sta già lavorando.

Dal 7/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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.
Lingua principale
Python
Stelle
65
Fork
28
Merge medio
4g 7h
PR unite (30g)
25

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenEnergyPlatform/oeplatform

Tutte le issue di OpenEnergyPlatform/oeplatform

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.