open-telemetry/opentelemetry-specification

OTLP: Recommended maximum backoff time for transient errors retry?

Open

#1,528 opened on Mar 10, 2021

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Makefile (987 forks)auto 404
enhancementhelp wantedrelease:allowed-for-gaspec:protocol

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

OTLP retry spec

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.

It is not clear what is the suggested maximum backoff time here. It would be good to have that in the spec otherwise SIGs may choose their own value(could be too high or too low) and will lead to inconsistency.

Contributor guide

Research direction
Determine recommended maximum backoff time based on industry standards and add to specification.
Tech stack
None
Domain
apinetworking
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Understanding of OTLP retry mechanism
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75