50ed370444
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]: b2bc41453b/instrumentation-api/src/main/java/io/opentelemetry/instrumentation/api/db/RedisCommandSanitizer.java
23 lines
799 B
Plaintext
23 lines
799 B
Plaintext
#####################################################
|
|
#
|
|
# 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
|
|
#
|
|
|
|
@open-telemetry/erlang-approvers
|
|
|
|
/instrumentation/opentelemetry_cowboy @bryannaegele @tsloughter
|
|
/instrumentation/opentelemetry_ecto @bryannaegele @tsloughter
|
|
/instrumentation/opentelemetry_oban @indrekj
|
|
/instrumentation/opentelemetry_phoenix @bryannaegele @tsloughter
|
|
/instrumentation/opentelemetry_redix @andrewhr
|
|
/utilities/opentelemetry_telemetry @bryannaegele @tsloughter
|