Skip to content

Don't retry telemetry on server error#72

Merged
brandonc merged 4 commits into
mainfrom
TF-38855-dont-retry-telemetry-on-429
Jun 30, 2026
Merged

Don't retry telemetry on server error#72
brandonc merged 4 commits into
mainfrom
TF-38855-dont-retry-telemetry-on-429

Conversation

@brandonc

Copy link
Copy Markdown
Collaborator

Description

By default, the otel http sink will retry if the server responds with a server error. This change disables the behavior.

PR Checklist

  • Run npx changie new or install changie to prepare a new changelog entry for the next set of release notes.
  • Ensure any command changes are sensitive to these global flags:
    • --json — Force machine readable output to stdout. Does not apply to stderr.
    • --markdown — Force markdown output to stdout. Does not apply to stderr.
    • --dry-run — Don't make any actual writes or other mutations. Describe what would have changed to stderr.
    • --quiet — Don't render output to stdout.
  • Get the logging interface from the context and add debug logging for interesting conditions and nonfatal situations.
  • Run make gen/screenshot if the root command output changes.
  • Add the Autocomplete field to positional arguments and flags to assist shell autocomplete.

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.

  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.

  • If applicable, I've documented the impact of any changes to security controls.

    Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

@brandonc brandonc changed the title Tf 38855 dont retry telemetry on 429 Don't retry telemetry on server error Jun 30, 2026
@brandonc brandonc merged commit 835e31b into main Jun 30, 2026
2 checks passed
@brandonc brandonc deleted the TF-38855-dont-retry-telemetry-on-429 branch June 30, 2026 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants