2021-04-19 17:21:49 +00:00
|
|
|
#####################################################
|
|
|
|
|
#
|
|
|
|
|
# List of approvers for OpenTelemetry Erlang repository
|
|
|
|
|
#
|
|
|
|
|
#####################################################
|
|
|
|
|
#
|
|
|
|
|
# Learn about membership in OpenTelemetry community:
|
|
|
|
|
# https://github.com/open-telemetry/community/blob/main/community-membership.md
|
|
|
|
|
#
|
|
|
|
|
#
|
|
|
|
|
# Learn about CODEOWNERS file format:
|
|
|
|
|
# https://help.github.com/en/articles/about-code-owners
|
|
|
|
|
#
|
|
|
|
|
|
2021-09-12 19:49:24 +00:00
|
|
|
@open-telemetry/erlang-approvers
|
|
|
|
|
|
2021-11-28 01:33:47 +00:00
|
|
|
/instrumentation/opentelemetry_cowboy @bryannaegele @tsloughter
|
2021-10-08 21:38:18 +00:00
|
|
|
/instrumentation/opentelemetry_ecto @bryannaegele @tsloughter
|
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 15:41:36 +00:00
|
|
|
/instrumentation/opentelemetry_oban @indrekj
|
2021-10-08 21:38:18 +00:00
|
|
|
/instrumentation/opentelemetry_phoenix @bryannaegele @tsloughter
|
2021-11-28 01:33:47 +00:00
|
|
|
/utilities/opentelemetry_telemetry @bryannaegele @tsloughter
|
