Error handling

The Prometheus exporter shouldn't just fail when an error happens. Instead it could just continue serving the metrics, log the incident and wait for the next update interval, or maybe even schedule a shorter interval. Hitting the rate limit would be such a case for example.

Start by locating the Prometheus exporter and its current error path. Review how update intervals and logging are handled, then clarify which recovery behavior is required for errors such as rate limits. Done means the exporter continues serving metrics, records the incident, and follows the agreed retry or scheduling behavior.

Written by the indexing model from the issue text.