You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We swallow errors making ECS task metadata API requests here and here. There is actually a way to surface errors to the caller: NewInvalidMetric.
I think we should use it so that errors are surfaced at write time, as in promhttp. The ECS APIs are supposed to be infallible, so the default behavior of serving an HTTP 500 on the /metrics request probably makes sense for everyone in all situations, though we could add a flag to control the behavior.
The text was updated successfully, but these errors were encountered:
We occasionally see the ECS APIs called by ecs_exporter 500 on the first
request or two, so the metrics served by the exporter are nonsense. By
using NewInvalidMetric in response to Collect, we can ensure that HTTP
500s are served on /metrics whenever such errors occur.
Closesprometheus-community#97.
Signed-off-by: Ian Kerins <[email protected]>
We swallow errors making ECS task metadata API requests here and here. There is actually a way to surface errors to the caller: NewInvalidMetric.
I think we should use it so that errors are surfaced at write time, as in promhttp. The ECS APIs are supposed to be infallible, so the default behavior of serving an HTTP 500 on the /metrics request probably makes sense for everyone in all situations, though we could add a flag to control the behavior.
The text was updated successfully, but these errors were encountered: