eecb238cff
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>
25 lines
590 B
Plaintext
25 lines
590 B
Plaintext
# The directory Mix will write compiled artifacts to.
|
|
/_build/
|
|
|
|
# If you run "mix test --cover", coverage assets end up here.
|
|
/cover/
|
|
|
|
# The directory Mix downloads your dependencies sources to.
|
|
/deps/
|
|
|
|
# Where third-party dependencies like ExDoc output generated docs.
|
|
/doc/
|
|
|
|
# Ignore .fetch files in case you like to edit your project deps locally.
|
|
/.fetch
|
|
|
|
# If the VM crashes, it generates a dump, let's ignore it too.
|
|
erl_crash.dump
|
|
|
|
# Also ignore archive artifacts (built via "mix archive.build").
|
|
*.ez
|
|
|
|
# Ignore package tarball (built via "mix hex.build").
|
|
opentelemetry_oban-*.tar
|
|
|