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
Alert notification provisioning error: alert notification with same name already exists #42229
Comments
is this a continuation of the topic you started in the forum? Is this an HA setup?... |
also see this thread for a related issue and possible fix: I will add some tags to your question in the forum and try to get some eyes on it |
Hi zuchka. It's similar. K8s starts on deployment first another pod before it destroys the old one. And the documentation states
Maybe I get something wrong here, but I would state that it's not working as described and expected. How is this supposed to work? |
@manfred-ackermann can you please provide some more information:
Thanks |
Yes ... started with an empty DB.
7 provisioned channels in total:
Yes... Instantly starts.
No, but I assume it's the same as of now, what would be:
Next time I scale down Grafana deployment to 0 and do another table export.
Can't do it now as of ongoing BlackFriday/Cybermonday insanity but will deliver on upcoming Tuesday. |
Sorry for the late response. Finally have set Grafana into log level debug ... Maybe only
has relevanz... After As I'm not sure about relevanz, here the full log (435 lines)
|
I think I see what's going on here. The uid We should probably improve this behavior to throw error if length is greater than 40 and not just silently continue. |
Will do so tomorrow and let you know of the outcome. |
Shortened all provisioned notifier uid to below 41 chars and had to truncate table Thanks @marefr for getting this detail! Issue is fixed from my side.
Second that. Also a note in the documentation may be of value. |
Thanks. Opened #42680 |
What happened:
Changed Grafana setup to use MySQL as DB instead of default SQLite3 to counter "database is locked" issue. When Grafana tries to restart it errors out with
as we also have sidecar notifiers enabled and only starts after executing
on the MySQL DB.
What you expected to happen:
I expected Grafana to updated or recreate the alert notification if it already exist in the DB.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
-/-
Environment:
The text was updated successfully, but these errors were encountered: