Add visibility if scrape time > scrape interval

[mattdurham]

Request

In flow the scrape component should mark itself as unhealthy if the scrape interval > scrape length. Or some other obvious alerting.

Use case

Need more visibility into unhealthiness.

[rfratto]

Historical context:

This is part of an overall debate for if the health of prometheus.scrape should depend on the scrape targets.

This was something we discussed early on, and the initial decision was no: just because a target collected by prometheus.scrape is unhealthy/timing out doesn't mean that prometheus.scrape itself is misbehaving.

We could revisit that decision, or we could find other ways to surface the problem as a metric/log/trace/etc.

[github-actions]

This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!