-
Notifications
You must be signed in to change notification settings - Fork 11.7k
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
Unified Alerting: contact-points/export/ returns EOF #88017
Comments
I've also hit this problem on version 10.4.1. |
Which backend do you use? |
We're just using the sqlite backend. |
I got this export to work by adding the |
Thank you for reporting this issue @andrejshapal Test in v10.2.1 (no issue)
Test in v10.4.1 (issue can be reproduced)
|
What happened?
Hello,
When trying to get manifest of contact points I am getting EOF (any option in UI and via API).
https://.../api/v1/provisioning/contact-points/export/
{"message":"EOF","traceID":""}
At the same time, the rest of simmilar exports (dashboard, alert rule) works without any issues.
I turned on debug logging, but did not find anything related.
The errors are:
At the same time, alerts are working without any issues.
I have tried 10.4.1, 10.4.4 and 11.0.0. All had the same issue.
At the same time, I have instance on 10.4.1 which don't have this issue. The difference between instances: one is deployed with grafana operator and uses postgres backend. The one without issues has sqllite.
But I did not find any difference in db payload:
The config in general is the same in both grafanas except db part.
I did check db logs for errors and did not find any.
What did you expect to happen?
/api/v1/provisioning/contact-points/export should return manifest
Did this work before?
This is my first usage of this functionality.
How do we reproduce it?
I am not sure. If the issue is in postgres, then it should be replicatable just switching be to psql.
But this looks like something wrong in code (serialization maybe) because simmilar api endpoints works without any issues.
Is the bug inside a dashboard panel?
No response
Environment (with versions)?
No response
Grafana platform?
Kubernetes
Datasource(s)?
No response
The text was updated successfully, but these errors were encountered: