opentelemetry-erlang-contrib/instrumentation/opentelemetry_oban
Yordis Prieto b12a464b5f
fix: setting oban attributes (#247)
* fix: passing custom oban attributes to span
2024-02-14 09:47:07 -07:00
..
lib fix: setting oban attributes (#247) 2024-02-14 09:47:07 -07:00
test fix: setting oban attributes (#247) 2024-02-14 09:47:07 -07:00
.formatter.exs Add opentelemetry integration to Oban (#6) 2021-12-08 08:41:36 -07:00
.gitignore Add opentelemetry integration to Oban (#6) 2021-12-08 08:41:36 -07:00
CHANGELOG.md fix: setting oban attributes (#247) 2024-02-14 09:47:07 -07:00
LICENSE Add opentelemetry integration to Oban (#6) 2021-12-08 08:41:36 -07:00
README.md Remove doc about function that is not being only a proxy (#253) 2024-01-18 14:39:07 -07:00
docker-compose.yml Update postgres Docker tag to v16.2 (#281) 2024-02-13 18:27:16 -07:00
mix.exs fix: setting oban attributes (#247) 2024-02-14 09:47:07 -07:00
mix.lock Update all library deps (#286) 2024-02-13 22:24:49 -07:00

README.md

OpentelemetryOban

OpentelemetryOban uses telemetry handlers to create OpenTelemetry spans from Oban events.

Installation

The package can be installed by adding opentelemetry_oban to your list of dependencies in mix.exs:

def deps do
  [
    {:opentelemetry_oban, "~> 1.0"}
  ]
end

In your application start:

    def start(_type, _args) do
      OpentelemetryOban.setup()

      # ...
    end

Usage

By default a new trace is automatically started when a job is processed.

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:

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

After:

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

Oban also supports inserting jobs using Oban.insert/4 and Oban.insert_all/4. These are currently not supported by OpentelemetryOban and are just proxied through to Oban.