otel-cf-workers

otel-cf-workers copied to clipboard

Hey @evanderkoogh, This instruments websocket message and close handling.  This is a pretty hacky PR and I would appreciate your feedback on how to make it ready to merge...

Ankcorn

Implement WFP instrumentation

2

Hi :wave:, In theory, this PR implements auto-instrumentation for WfP. The only part I'm unhappy about is the attribute parser, but since the parameter types are `unknown`, I guess it's...

DaniFoldi

test scaffolding and DO storage instrumentation tests

6

This PR introduces [Vitest](https://vitest.dev/) with initial unit tests covering Durable Object storage instrumentation. These tests are focused on verifying the resulting spans match the expected behavior. In writing these tests,...

rtbenfield

[Feature request] Support for websocket (and hibernation API)

7

After investigating more https://github.com/evanderkoogh/otel-cf-workers/issues/14#issuecomment-1625437208, it looks like this module doesn't support yet Websockets and using the DO storage in a websocket handler throws the error: ``` Cannot read properties of...

SamyPesse

Protobuffer support

8

Love the start of the library! We use Dynatrace as part of our monitoring stack and presently they only support HTTP & Protobuffer as a transport mechanism for span traces...

cdloh

Split up README into seperate docs

4

Right now especially the configuration section explains a lot of how Open Telemetry works to explain what to configure and how. This can all be put into a separate doc...

evanderkoogh

`Promise will never complete` when instrumenting worker

6

We have a pretty complex cloudflare worker that we recently added instrumentation to with `otel-cf-workers`. The library has worked like a dream, providing extra insight into our requests. However, when...

jmaroeder

We are using `QStash` and would like to setup distributed tracing across jobs. Unfortunately, QStash adds a prefix to the custom headers. Afaik, this library extracts potential parent traces from...

psteinroe

Allow custom resource attributes

5

Hey, here's the situation: - We're sending traces to Grafana Tempo - We want to use its `deployment.environment` resource attribute to split traces between stages - https://grafana.com/docs/grafana-cloud/monitor-applications/application-observability/manual/inventory/#deployment-environment ![CleanShot 2024-05-31 at...

jasonkuhrt

This wasted some of my time and probably others. It's not obvious at all. This could be worth a mention in these docs whilst the issue still exists. https://github.com/cloudflare/workerd/issues/2247

jasonkuhrt