Skip to content

OTEL Exporter endpoint unavailable makes worker itself unstable #205

@oskarm93

Description

@oskarm93

I had an issue yesterday where the endpoint I used in the exporter configuration was slow or unavailable, throwing 503s.
During that time, P99 latency on my workers spiked to >15s without an obvious cause (because calls to the exporter aren't traced).

Is what I observed expected?

I checked the exporter code, and it uses a fetch call to send telemetry, but that means the worker cannot finish until that fetch call is completed?

unwrap(fetch)(this.url, params)

This would impact latency and availability of the worker. I know you can schedule some calls to complete for after the worker returns to client, e.g. with waitUntil.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions