-
Notifications
You must be signed in to change notification settings - Fork 59
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
Configure Datasource returns error #151
Comments
same here 👋 |
You use Grafana Mimir Alertmanager, not Prometheus Alertmanager. Same issue for me. |
Same for me on Grafana 11. Looks like it's making a request to Grafana itself (see Not using mimir. |
I have a hard time believing this, but what solved this problem for me was to not name my datasource of type camptocamp-prometheus-alertmanager-datasource "alertmanager". In my case, URL was set to If my datasource was named "alertmanager", I would see a request in the request log of grafana itself where it received a request for /alertmanager, i.e, it seems like for some reason, the http request was not routed to my actual alertmanager, but to grafana. If I instead name my datasource "camptocamp-prometheus-alertmanager-datasource", it starts working. This seems to appeared somewhere between Grafana 9.0.5 and Grafana 11.0.0. Oddly enough, this was only a problem on one of my Grafana instances. |
Hello,
After installing the plugin and configuring the datasource I get the following red error message:
My Datasource Details:
![image](https://private-user-images.githubusercontent.com/51332147/282698376-65379f0c-6e25-4967-bc49-2ee38b7780fd.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk0ODM2NzksIm5iZiI6MTczOTQ4MzM3OSwicGF0aCI6Ii81MTMzMjE0Ny8yODI2OTgzNzYtNjUzNzlmMGMtNmUyNS00OTY3LWJjNDktMmVlMzhiNzc4MGZkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEzVDIxNDkzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWY2NTljNWQxZGRmOGIwNWExM2Y2MzhmYTI4ZmMxYmVhZTQ3NjQwMDY3NjVhMTZjYmMzMzJkODI2MTFhMGEzZmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ZM8bvhTs731ZR7AF39JGOFxdJ_pHo-EeIXk7LARW2zc)
The text was updated successfully, but these errors were encountered: