shadowfacts
/
opentelemetry-erlang-contrib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
opentelemetry-erlang-contrib/instrumentation/opentelemetry_redix/mix.lock

25 lines
6.1 KiB
Plaintext
Raw Normal View History

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
%{
"acceptor_pool": {:hex, :acceptor_pool, "1.0.0", "43c20d2acae35f0c2bcd64f9d2bde267e459f0f3fd23dab26485bf518c281b21", [:rebar3], [], "hexpm", "0cbcd83fdc8b9ad2eee2067ef8b91a14858a5883cb7cd800e6fcd5803e158788"},
update elixir package deps (#126) * update elixir package deps * Oban test updates
2022-11-16 00:48:50 +00:00
"chatterbox": {:hex, :ts_chatterbox, "0.13.0", "6f059d97bcaa758b8ea6fffe2b3b81362bd06b639d3ea2bb088335511d691ebf", [:rebar3], [{:hpack, "~>0.2.3", [hex: :hpack_erl, repo: "hexpm", optional: false]}], "hexpm", "b93d19104d86af0b3f2566c4cba2a57d2e06d103728246ba1ac6c3c0ff010aa7"},
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
"ctx": {:hex, :ctx, "0.6.0", "8ff88b70e6400c4df90142e7f130625b82086077a45364a78d208ed3ed53c7fe", [:rebar3], [], "hexpm", "a14ed2d1b67723dbebbe423b28d7615eb0bdcba6ff28f2d1f1b0a7e1d4aa5fc2"},
update elixir package deps (#126) * update elixir package deps * Oban test updates
2022-11-16 00:48:50 +00:00
"dialyxir": {:hex, :dialyxir, "1.2.0", "58344b3e87c2e7095304c81a9ae65cb68b613e28340690dfe1a5597fd08dec37", [:mix], [{:erlex, ">= 0.2.6", [hex: :erlex, repo: "hexpm", optional: false]}], "hexpm", "61072136427a851674cab81762be4dbeae7679f85b1272b6d25c3a839aff8463"},
"earmark_parser": {:hex, :earmark_parser, "1.4.29", "149d50dcb3a93d9f3d6f3ecf18c918fb5a2d3c001b5d3305c926cddfbd33355b", [:mix], [], "hexpm", "4902af1b3eb139016aed210888748db8070b8125c2342ce3dcae4f38dcc63503"},
Bump dependencies and relax opentelemetry* to 1.0 (#75)
2022-03-31 17:23:32 +00:00
"erlex": {:hex, :erlex, "0.2.6", "c7987d15e899c7a2f34f5420d2a2ea0d659682c06ac607572df55a43753aa12e", [:mix], [], "hexpm", "2ed2e25711feb44d52b17d2780eabf998452f6efda104877a3881c2f8c0c0c75"},
update elixir package deps (#126) * update elixir package deps * Oban test updates
2022-11-16 00:48:50 +00:00
"ex_doc": {:hex, :ex_doc, "0.28.6", "2bbd7a143d3014fc26de9056793e97600ae8978af2ced82c2575f130b7c0d7d7", [:mix], [{:earmark_parser, "~> 1.4.19", [hex: :earmark_parser, repo: "hexpm", optional: false]}, {:makeup_elixir, "~> 0.14", [hex: :makeup_elixir, repo: "hexpm", optional: false]}, {:makeup_erlang, "~> 0.1", [hex: :makeup_erlang, repo: "hexpm", optional: false]}], "hexpm", "bca1441614654710ba37a0e173079273d619f9160cbcc8cd04e6bd59f1ad0e29"},
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
"gproc": {:hex, :gproc, "0.8.0", "cea02c578589c61e5341fce149ea36ccef236cc2ecac8691fba408e7ea77ec2f", [:rebar3], [], "hexpm", "580adafa56463b75263ef5a5df4c86af321f68694e7786cb057fd805d1e2a7de"},
update elixir package deps (#126) * update elixir package deps * Oban test updates
2022-11-16 00:48:50 +00:00
"grpcbox": {:hex, :grpcbox, "0.16.0", "b83f37c62d6eeca347b77f9b1ec7e9f62231690cdfeb3a31be07cd4002ba9c82", [:rebar3], [{:acceptor_pool, "~>1.0.0", [hex: :acceptor_pool, repo: "hexpm", optional: false]}, {:chatterbox, "~>0.13.0", [hex: :ts_chatterbox, repo: "hexpm", optional: false]}, {:ctx, "~>0.6.0", [hex: :ctx, repo: "hexpm", optional: false]}, {:gproc, "~>0.8.0", [hex: :gproc, repo: "hexpm", optional: false]}], "hexpm", "294df743ae20a7e030889f00644001370a4f7ce0121f3bbdaf13cf3169c62913"},
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
"hpack": {:hex, :hpack_erl, "0.2.3", "17670f83ff984ae6cd74b1c456edde906d27ff013740ee4d9efaa4f1bf999633", [:rebar3], [], "hexpm", "06f580167c4b8b8a6429040df36cc93bba6d571faeaec1b28816523379cbb23a"},
Bump dependencies and relax opentelemetry* to 1.0 (#75)
2022-03-31 17:23:32 +00:00
"makeup": {:hex, :makeup, "1.1.0", "6b67c8bc2882a6b6a445859952a602afc1a41c2e08379ca057c0f525366fc3ca", [:mix], [{:nimble_parsec, "~> 1.2.2 or ~> 1.3", [hex: :nimble_parsec, repo: "hexpm", optional: false]}], "hexpm", "0a45ed501f4a8897f580eabf99a2e5234ea3e75a4373c8a52824f6e873be57a6"},
"makeup_elixir": {:hex, :makeup_elixir, "0.16.0", "f8c570a0d33f8039513fbccaf7108c5d750f47d8defd44088371191b76492b0b", [:mix], [{:makeup, "~> 1.0", [hex: :makeup, repo: "hexpm", optional: false]}, {:nimble_parsec, "~> 1.2.3", [hex: :nimble_parsec, repo: "hexpm", optional: false]}], "hexpm", "28b2cbdc13960a46ae9a8858c4bebdec3c9a6d7b4b9e7f4ed1502f8159f338e7"},
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
"makeup_erlang": {:hex, :makeup_erlang, "0.1.1", "3fcb7f09eb9d98dc4d208f49cc955a34218fc41ff6b84df7c75b3e6e533cc65f", [:mix], [{:makeup, "~> 1.0", [hex: :makeup, repo: "hexpm", optional: false]}], "hexpm", "174d0809e98a4ef0b3309256cbf97101c6ec01c4ab0b23e926a9e17df2077cbb"},
Bump dependencies and relax opentelemetry* to 1.0 (#75)
2022-03-31 17:23:32 +00:00
"nimble_parsec": {:hex, :nimble_parsec, "1.2.3", "244836e6e3f1200c7f30cb56733fd808744eca61fd182f731eac4af635cc6d0b", [:mix], [], "hexpm", "c8d789e39b9131acf7b99291e93dae60ab48ef14a7ee9d58c6964f59efb570b0"},
update elixir package deps (#126) * update elixir package deps * Oban test updates
2022-11-16 00:48:50 +00:00
"opentelemetry": {:hex, :opentelemetry, "1.1.2", "77ba2fd2fee67bebde590851a4afeda45b3f298310aa410a2a3804b364cb598a", [:rebar3], [{:opentelemetry_api, "~> 1.1", [hex: :opentelemetry_api, repo: "hexpm", optional: false]}], "hexpm", "5c60be189d6aed64a9fd17055f72c93eab144be441e625276c3c95533e6bb4c7"},
"opentelemetry_api": {:hex, :opentelemetry_api, "1.1.1", "3b43877c456c8a7f5448a95d9bf4fb4bb8cc2abbbea2c62d5f8e8c538b4af14f", [:mix, :rebar3], [], "hexpm", "a9554b3208b60a70043318d051ea78fbbc7a1b8f4c418ebc16ccb40015995675"},
"opentelemetry_exporter": {:hex, :opentelemetry_exporter, "1.2.2", "3966c56656627ef7db6c34c4ce28d44ac8629dcd065a310d7c33712fc2a1cfe3", [:rebar3], [{:grpcbox, ">= 0.0.0", [hex: :grpcbox, repo: "hexpm", optional: false]}, {:opentelemetry, "~> 1.1", [hex: :opentelemetry, repo: "hexpm", optional: false]}, {:opentelemetry_api, "~> 1.1", [hex: :opentelemetry_api, repo: "hexpm", optional: false]}, {:tls_certificate_check, "~> 1.11", [hex: :tls_certificate_check, repo: "hexpm", optional: false]}], "hexpm", "5c11adeda19e0d203a04efe92cdd7a183da4b09ae8acaba7608e9303fa258e74"},
fix: missing deps in redix (#122)
2022-11-15 11:43:44 +00:00
"opentelemetry_semantic_conventions": {:hex, :opentelemetry_semantic_conventions, "0.1.0", "0a7463c0ec4541d9c8e09ee99bd7b5480fa6f90f40313a6d071fd7521b5a712f", [:mix, :rebar3], [], "hexpm", "eccf41bc7afec299484075aff570bf504a2f7e5c38fbcdaceb33a6d6b901448d"},
update elixir package deps (#126) * update elixir package deps * Oban test updates
2022-11-16 00:48:50 +00:00
"redix": {:hex, :redix, "1.2.0", "0d7eb3ccb7b82c461a6ea28b65c2c04486093d816dd6d901a09164800e004df1", [:mix], [{:castore, "~> 0.1.0", [hex: :castore, repo: "hexpm", optional: true]}, {:telemetry, "~> 0.4.0 or ~> 1.0", [hex: :telemetry, repo: "hexpm", optional: false]}], "hexpm", "e1e0deb14599da07c77e66956a12863e85ee270ada826804a0ba8e61657e22a3"},
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
"ssl_verify_fun": {:hex, :ssl_verify_fun, "1.1.6", "cf344f5692c82d2cd7554f5ec8fd961548d4fd09e7d22f5b62482e5aeaebd4b0", [:make, :mix, :rebar3], [], "hexpm", "bdb0d2471f453c88ff3908e7686f86f9be327d065cc1ec16fa4540197ea04680"},
Relax requirement on telemetry library (#77)
2022-04-13 15:57:45 +00:00
"telemetry": {:hex, :telemetry, "1.1.0", "a589817034a27eab11144ad24d5c0f9fab1f58173274b1e9bae7074af9cbee51", [:rebar3], [], "hexpm", "b727b2a1f75614774cff2d7565b64d0dfa5bd52ba517f16543e6fc7efcc0df48"},
update elixir package deps (#126) * update elixir package deps * Oban test updates
2022-11-16 00:48:50 +00:00
"tls_certificate_check": {:hex, :tls_certificate_check, "1.16.0", "45b05e3b993dbace2e4ebccb666eadbd038f1da8f4db9691f4f34a274dfb0bd7", [:rebar3], [{:ssl_verify_fun, "1.1.6", [hex: :ssl_verify_fun, repo: "hexpm", optional: false]}], "hexpm", "3dc0508c749619b8d6a5e21aca4d719c184f065541795b0556398c8e574a3064"},
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
}