opentelemetry-erlang-contrib/instrumentation
Indrek Juhkam eecb238cff
Add opentelemetry integration to Oban (#6)
By default a new trace is automatically started when a job is processed
by monitoring these events:
* `[:oban, :job, :start]` — at the point a job is fetched from the database and will execute
* `[:oban, :job, :stop]` — after a job succeeds and the success is recorded in the database
* `[:oban, :job, :exception]` — after a job fails and the failure is recorded in the database

To also record a span when a job is created and to link traces together
`Oban.insert/2` has to be replaced by `OpentelemetryOban.insert/2`.

Before:

```elixir
  %{id: 1, in_the: "business", of_doing: "business"}
  |> MyApp.Business.new()
  |> Oban.insert()
```

After:

```elixir
  %{id: 1, in_the: "business", of_doing: "business"}
  |> MyApp.Business.new()
  |> OpentelemetryOban.insert()
```

Co-authored-by: Tristan Sloughter <t@crashfast.com>
2021-12-08 08:41:36 -07:00
..
opentelemetry_cowboy Publish packages (#28) 2021-10-15 14:01:11 -06:00
opentelemetry_ecto Set error status for ecto errors in opentelemetry_ecto (#41) 2021-11-22 12:08:31 -07:00
opentelemetry_oban Add opentelemetry integration to Oban (#6) 2021-12-08 08:41:36 -07:00
opentelemetry_phoenix opentelemetry_phoenix http.status -> http_status_code (#42) 2021-11-19 07:15:43 -07:00