Skip to content
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

Expose Alloy overall component health via HTTP endpoint #2061

Closed
thampiotr opened this issue Nov 11, 2024 · 1 comment · Fixed by #2197
Closed

Expose Alloy overall component health via HTTP endpoint #2061

thampiotr opened this issue Nov 11, 2024 · 1 comment · Fixed by #2197
Assignees
Labels
enhancement New feature or request frozen-due-to-age

Comments

@thampiotr
Copy link
Contributor

Request

Expose via an HTTP endpoint the overall health of all running components: if at least one component is not healthy - return an error.

For example, if I request

GET /-/ready?strict=true

And there is one component failing, we should get back:

503: Component 'foo.bar.baz' is not healthy: 'error message'

Use case

Sometimes users may want to set up a liveness or readiness probe on Alloy in k8s that does not only check if Alloy runtime is started, but also checks that all the components are healthy.

Currently Alloy's /-/ready endpoint will return 200 even if there are components failing to start. This can be useful when we have multiple pipelines and want the healthy ones to continue running. But some users may prefer a "fail hard" behaviour.

@thampiotr thampiotr added the enhancement New feature or request label Nov 11, 2024
@DWebb0
Copy link

DWebb0 commented Nov 19, 2024

I'm registering my interest here.

@ptodev ptodev self-assigned this Nov 26, 2024
@ptodev ptodev linked a pull request Nov 29, 2024 that will close this issue
4 tasks
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 11, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request frozen-due-to-age
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants