shadowfacts
/
opentelemetry-erlang-contrib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
opentelemetry-erlang-contrib/CODEOWNERS

25 lines
903 B
Plaintext
Raw Normal View History

Create CODEOWNERS
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
#
Otel phoenix migration (#4) * Otel phoenix migration * Abandon dynamic matrix for now * Add project-level codeowners * Add examples and phoenix * Typo
2021-09-12 19:49:24 +00:00
@open-telemetry/erlang-approvers
Migrate otel_telemetry to contrib (#43)
2021-11-28 01:33:47 +00:00
/instrumentation/opentelemetry_cowboy @bryannaegele @tsloughter
Migrate otel ecto (#16) * Migrate otel ecto
2021-10-08 21:38:18 +00:00
/instrumentation/opentelemetry_ecto @bryannaegele @tsloughter
Add Nebulex instrumentation library (#83) Add instrumentation for Nebulex, a distributed cache library. This library provides solid telemetry support for this initial implementation. Caching implementation is mostly based on in-memory storage (like ETS) and RPC calls for distribution (via OTP libraries, like :erpc). AFAICT, there is not much specifics for how to translate into Semantic Attributes: those caches are not quite a DB, except maybe for the one which implements the storage; the RPC can't be reliably captured either. Given the above constraints, this initial implementation instruments the library via custom attributes (namespaced as `nebulex.*`). It's not 100% clear the behaviour of OTel for actual distributed caches - from my tests, that may create some orphan spans. I think that's fine as first release. Nebulex follow the patterns of Ecto, so this instrumentation follows a similar pattern of OpentelemetryEcto. It does include a `setup_all/1` function for convenience, that leverages the :init events Nebulex emit on process start. Co-authored-by: Tristan Sloughter <t@crashfast.com>
2022-12-15 00:38:18 +00:00
/instrumentation/opentelemetry_nebulex @andrewhr
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
Migrate otel ecto (#16) * Migrate otel ecto
2021-10-08 21:38:18 +00:00
/instrumentation/opentelemetry_phoenix @bryannaegele @tsloughter
Add OpenTelemetry integration to Redix (#29) Initial approach follows Ecto instrumentation, recording spans for all Redix `[:redix, :pipeline, :stop]` events. The command sanitization is inspired-by and adapted from [Java instrumentation][1], from where I've also copied the actual commands and what configuration should they follow. Network attributes are tracked via a "sidecar" process, which keeps track of connection attributes also via `telemetry`. This extra bit of bookkeeping is needed as command events doesn't include that piece of information, unfortunately. [1]: https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/b2bc41453bec7df15a45a78b29709fdf634e4643/instrumentation-api/src/main/java/io/opentelemetry/instrumentation/api/db/RedisCommandSanitizer.java
2022-01-04 21:39:19 +00:00
/instrumentation/opentelemetry_redix @andrewhr
Migrate otel_telemetry to contrib (#43)
2021-11-28 01:33:47 +00:00
/utilities/opentelemetry_telemetry @bryannaegele @tsloughter
Add otel tesla library (#90) * Add Tesla HTTP client instrumentation library * Update workflows configuration * Update labeler.yml * Update CODEOWNERS * Add LICENSE file Co-authored-by: Bryan Naegele <bryannaegele@users.noreply.github.com>
2022-08-25 18:47:59 +00:00
/instrumentation/opentelemetry_tesla @ricardoccpaiva