No description
Graham McIntire
f446977048
PromEx.Plugins.Oban counts job exceptions as a Prometheus counter but does not tell us which worker/queue failed, whether the job is about to be retried, or the exception class. This adds a telemetry handler on [:oban, :job, :exception] that: - emits a single structured Logger.error with worker, queue, job_id, attempt, max_attempts, retry_exhausted?, kind, reason class, and args-keys summary (never values — args can contain PII/tokens); - dispatches opt-in per-worker recovery callbacks (on_permanent_failure/1 when retries exhausted, on_transient_failure/1 otherwise); - catches callback failures so a bug in one worker's recovery path cannot detach the handler or break logging for other jobs; - does not emit a second telemetry event, so PromEx counts are not double-counted. Handler is attached from Application.start/2 after the Oban supervisor starts. |
||
|---|---|---|
| .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