No description
Adds the OTel deps (opentelemetry + exporter + phoenix / ecto / oban / bandit auto-instrumentation helpers) and attaches them in Application.start/2 so the existing Phoenix, Ecto, Oban, and Bandit telemetry events flow as OTLP spans without any call-site changes. Exporter config is gated on OTEL_EXPORTER_OTLP_ENDPOINT in config/runtime.exs — set in the k8s manifests to the cluster collector (otel-collector.observability.svc.cluster.local:4317). When unset we switch traces_exporter to :none so nothing is shipped; dev/test stays quiet. Resource attributes tag spans with service.name=microwaveprop and service.namespace=prop, matching the Rust workers' attribute shape so Tempo can group the full hourly chain across both languages. Both the main prop deployment and the backfill deployment get the env; backfill is still a full BEAM node running enrichment workers, so its Oban/Ecto spans are worth seeing too. |
||
|---|---|---|
| .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