-
Notifications
You must be signed in to change notification settings - Fork 404
Metric last_state persists after ExternalSecret deleted #399
Comments
Would love a fix for this too :) The line is here: Once the gauge is set, it needs to be explicitly unset or removed when the external secret is removed. I think One workaround is to restart the external secret daemon when you see the bad gauge. |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. |
This bug is still around |
Yeah would love to see a fix for this, its impacting the monitoring of our secrets |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. |
This still haunts our monitoring checks - could you please look into this? |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
While this is still unfortunate please see #864 |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. |
Great new metric last_state, thanks!
We now have a monitoring rule is in place to watch for failed sync. A sync was failing so I deleted the ExternalSecret. However, last_state does not forget and continues to report -1 on the ExternalSecret that no longer exists. It continues to report success on deleted objects as well.
Clearly this is bad and last_state should stop reporting ExternalSecrets status when they go away.
The text was updated successfully, but these errors were encountered: