I was able to use the API to GET all my alerts (created manually in the Grafana UI) by logging into Grafana and then using: http://[IP_ADDRESS]/api/ruler/grafana/api/v1/rules. This gave me a json that contained all of my alerts created in Grafana. I then tried to upload that json directly into another env using curl -XPOST -H "Authorization: Bearer [MY_TOKEN]" -i [MY_URL]/api/v1/provisioning/alert-rules --data-binary @./api-log-alerts.json -H "Content-Type: application/json which failed because the API does not take the entire group at a time (WE NEED THAT FEATURE!). So I created a new JSON with a single rule (that I cut and pasted from the rules section of the main file), and was able to upload the file after a couple fixes to remove non-mandetory fields, and I got this response:
HTTP/1.1 201 Created
Cache-Control: no-cache
Content-Type: application/json
Expires: -1
Pragma: no-cache
X-Content-Type-Options: nosniff
X-Frame-Options: deny
X-Xss-Protection: 1; mode=block
Date: Thu, 26 Jan 2023 17:25:53 GMT
Content-Length: 1452
Via: 1.1 google
The interesting thing is that the alert created with the API command DOES NOT APPEAR in the Grafana UI Alert console list [MY_URL]/alerting/list and it does not appear in the API call to get all of the alerts, but they are still firing!!!
Has anyone here successfully created an alert using the API? Is there a way to configure these as config files in my cluster so they just exist when I deploy the pod?
Thanks