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
{{ message }}
This repository has been archived by the owner on Jul 26, 2022. It is now read-only.
Hi - thanks for exposing so many useful metrics out of the box! I just wanted to check my understanding of something I've observed and see if there's a way around it.
I made a prometheus rule to send an alert whenever an external secret had a failed last sync with the below:
I made a dummy secret which would always fail (upstream secret doesn't exist), and I received the alert - all good.
I then deleted the dummy secret, but the alert still fires. It seems as though if there was never a successful sync after the most recent failed sync, this metric is always present.
Is there a way to avoid this?
The text was updated successfully, but these errors were encountered:
Hi - thanks for exposing so many useful metrics out of the box! I just wanted to check my understanding of something I've observed and see if there's a way around it.
I made a prometheus rule to send an alert whenever an external secret had a failed last sync with the below:
I made a dummy secret which would always fail (upstream secret doesn't exist), and I received the alert - all good.
I then deleted the dummy secret, but the alert still fires. It seems as though if there was never a successful sync after the most recent failed sync, this metric is always present.
Is there a way to avoid this?
The text was updated successfully, but these errors were encountered: