View Source OpentelemetryOban (opentelemetry_oban v1.1.0)

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

Supported events include job start/stop and also when an exception is raised.

Usage

In your application start:

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

  # ...
end

Summary

Functions

insert(name \\ Oban, changeset)
insert(name \\ Oban, multi, multi_name, changeset_or_fun)
insert!(name \\ Oban, changeset)
insert_all(name \\ Oban, changesets_or_wrapper)
insert_all(name \\ Oban, multi, multi_name, changesets_or_wrapper)
setup(opts \\ [])

Initializes and configures telemetry handlers.

Functions

Link to this function

insert(name \\ Oban, changeset)

View Source
Link to this function

insert(name \\ Oban, multi, multi_name, changeset_or_fun)

View Source
Link to this function

insert!(name \\ Oban, changeset)

View Source
Link to this function

insert_all(name \\ Oban, changesets_or_wrapper)

View Source
Link to this function

insert_all(name \\ Oban, multi, multi_name, changesets_or_wrapper)

View Source
Link to this function

setup(opts \\ [])

View Source

Initializes and configures telemetry handlers.

By default jobs and plugins are traced. If you wish to trace only jobs then use:

OpentelemetryOban.setup(trace: [:jobs])

Note that if you don't trace plugins, but inside the plugins, there are spans from other instrumentation libraries (e.g. ecto) then these will still be traced. This setting controls only the spans that are created by opentelemetry_oban.