Skip to content

[extension/healthcheckv2] Option to have healthcheck endpoint return 200 unless all pipelines are failing #39982

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kristinapathak opened this issue May 9, 2025 · 1 comment
Labels
enhancement New feature or request extension/healthcheckv2 needs triage New item requiring triage

Comments

@kristinapathak
Copy link
Contributor

Component(s)

extension/healthcheckv2

Is your feature request related to a problem? Please describe.

Currently, if at least one pipeline is failing, the v2 health endpoint will report an error status instead of OK.

Describe the solution you'd like

I'm interested in reporting OK as long as at least one pipeline is OK. If all pipelines are failing, then the current precedence of error statuses would be reported as the top level health.

Describe alternatives you've considered

Some alternatives:

  1. configuration logic that decides how to roll up errors from component level to pipeline level, then pipeline level to top level.
  2. a custom health endpoint maintained outside of otel that takes the detailed health status and provides the logic I described above.

Additional context

No response

@kristinapathak kristinapathak added enhancement New feature or request needs triage New item requiring triage labels May 9, 2025
Copy link
Contributor

github-actions bot commented May 9, 2025

Pinging code owners:

  • extension/healthcheckv2: @mwear

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request extension/healthcheckv2 needs triage New item requiring triage
Projects
None yet
Development

No branches or pull requests

1 participant