-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stateless Rule: Panic opening /alerts after alert state restored. Duplicate alertstate ? #6060
Comments
Hum found a misconfig where alerts are also fired by prometheus (and alerts state may restore to sidecar) |
@ahurtaud probably a long shot did but you find anything from your investigations? I'm seeing the exact same panic on my instance of thanos ruler |
We are not seeing the gopanic anymore, if I remember correctly it was definitely an issue where: |
thanks for the update @ahurtaud I deleted the PVC attached to the thanos ruler and it seemed to have cleared the error, so I think there was something odd going on in the persistence. I deleted it on thursday and haven't had a reoccurence since then. |
We've been hit with this. There is a fix for this in 0.32 |
Thanos, Prometheus and Golang version used:
v0.30.1
What happened:
I implemented the alert state restore in stateless ruler thanks to #5230
But the ruler after restart keeps the alert state for the firing ones but also create some matching pending alerts.
This issue makes the Alerts webpage to go panic (see full logs in details) because alerts have 2 states at once I think.
The pending alert have all the
'--restore-ignored-label
labels on top of the matching firing alert.for exemple
tenant_id
here (and all other labels I properly set as ignored)What you expected to happen:
Go Panic should not happen
Restored alerts should not create their corresponding Pending alerts with the ignored labels?
stateless ruler restart: (firing are ~kept), but pending are created.
Full logs to relevant components:
Anything else we need to know:
I hope I haven't made any configuration mistakes as it is quite difficult to configure:
below some interesting for investations flags:
The text was updated successfully, but these errors were encountered: