Skip to content

Additional specification around OTLP exporter retry requirements #1742

@jack-berg

Description

@jack-berg

What are you trying to achieve?

The OTLP exporter spec states the following concerning retry logic:

Transient errors MUST be handled with a retry strategy. This retry strategy MUST implement an exponential back-off with jitter to avoid overwhelming the destination until the network is restored or the destination has recovered.

There should be more specificity around how exactly the retry strategy should be configured with gRPC. Here's the proto definition for the gRPC Retry Policies. Without more specificity, language implementations may end up choosing arbitrary values for these parameters.

Perhaps there should also be configuration parameters for adjusting the retry parameters. Maybe retry can be enabled / disabled altogether, or maybe the various parameters can be tuned.

Additional context.

Discussing this in an opentelemetry-java issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    spec:protocolRelated to the specification/protocol directorytriage:deciding:needs-infoNot enough information. Left open to provide the author with time to add more details

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions