No description
New telemetry module wires tracing-subscriber to both a local JSON fmt layer (keeps kubectl-logs output identical) and an OpenTelemetry OTLP/gRPC exporter, activated only when OTEL_EXPORTER_OTLP_ENDPOINT is set. The returned TelemetryGuard holds the SdkTracerProvider until process shutdown so queued spans flush before exit. Both bin targets (worker, hrrr_point_worker) now call telemetry::init(service_name) at startup; service_name becomes the OTel service.name attribute so Tempo groups spans per binary. Tracing instrumentation on the three main work units: - pipeline::run_chain_step (forecast f01..f18) - pipeline::run_analysis_step (analysis f00) - hrrr_points::process_batch (per-QSO point drain) k8s manifests set OTEL_EXPORTER_OTLP_ENDPOINT to the cluster collector at otel-collector.observability.svc.cluster.local:4317. Backend wiring lives in the vntx-infra repo. |
||
|---|---|---|
| .forgejo/workflows | ||
| .github | ||
| assets | ||
| bin | ||
| config | ||
| docs | ||
| k8s | ||
| lib | ||
| lib_ml | ||
| notebooks | ||
| priv | ||
| rel | ||
| rust/prop_grid_rs | ||
| scripts | ||
| test | ||
| vendor | ||
| .credo.exs | ||
| .dockerignore | ||
| .formatter.exs | ||
| .gitignore | ||
| .tool-versions | ||
| AGENTS.md | ||
| algo.md | ||
| app.json | ||
| CLAUDE.md | ||
| Dockerfile | ||
| elevation.md | ||
| mix.exs | ||
| mix.lock | ||
| prediction.md | ||
| README.md | ||
| tail_logs.sh | ||
| updates.md | ||
Microwaveprop
To start your Phoenix server:
- Run
mix setupto install and setup dependencies - Start Phoenix endpoint with
mix phx.serveror inside IEx withiex -S mix phx.server
Now you can visit localhost:4000 from your browser.
Ready to run in production? Please check our deployment guides.
Learn more
- Official website: https://www.phoenixframework.org/
- Guides: https://hexdocs.pm/phoenix/overview.html
- Docs: https://hexdocs.pm/phoenix
- Forum: https://elixirforum.com/c/phoenix-forum
- Source: https://github.com/phoenixframework/phoenix