Alloy UI always returns healthy

[mrethers]

What's wrong?

Hi team,

I haven't seen a scenario where this UI returns unhealthy. Not sure what qualifies but I have these 3 screens which are at odds with each other I think. I would expect those 2 components to be unhealthy:

Steps to reproduce

Add an invalid scrape target or remote URL

System information

No response

Software version

No response

Configuration

Logs

[mattdurham]

Scrape is working as expected, the component is healthy but the endpoints are not. By default a component is healthy if it successfully started, specific components can override this behavior. For scraping we dont consider the individual scrapes to derive component health. There are environments where a scraping can be scraping 10,000+ endpoints and there is almost always one failing.

[mattdurham]

The remote_write error not triggering unhealthy I can get behind it being incorrect.

[mrethers]

What would be a unhealthy state for a scrape in that case?

[mattdurham]

For the scraper if it starts with a valid configuration its healthy, if you want to monitor scrape jobs the up indicator would be the path to go with.