summaryrefslogtreecommitdiffstats
path: root/tools/docker-compose
diff options
context:
space:
mode:
authorElijah DeLee <kdelee@redhat.com>2022-09-07 19:01:10 +0200
committerElijah DeLee <kdelee@redhat.com>2022-09-14 22:23:53 +0200
commit10d06f219d0b4076798b350bd94d05e4d602b2bf (patch)
treeecc4eec3df236e85bd62e2f5707b26de73a560df /tools/docker-compose
parentMerge pull request #12868 from keithjgrant/12853-ws-event-duplication (diff)
downloadawx-10d06f219d0b4076798b350bd94d05e4d602b2bf.tar.xz
awx-10d06f219d0b4076798b350bd94d05e4d602b2bf.zip
add alerting rule to grafana
This rule alerts if the redis queue is larger than what the rolling average event insertion rate/second * 120. In other words, if the redis queue is larger than it appears we can process events in two minutes. It appears it has to meet this condition for 60 seconds to start firing. Future commits will address how to configure contact points like slack. shout out to @jainnikhil30 and @rebeccahhh who figured this out in jam session this morning.
Diffstat (limited to 'tools/docker-compose')
-rw-r--r--tools/docker-compose/README.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/tools/docker-compose/README.md b/tools/docker-compose/README.md
index e13b54a369..9080a6339b 100644
--- a/tools/docker-compose/README.md
+++ b/tools/docker-compose/README.md
@@ -480,3 +480,8 @@ $ PROMETHEUS=yes GRAFANA=yes make docker-compose
3. Navigate to `http://localhost:3001`. Sign in, using `admin` for both username and password.
4. In the left navigation menu go to Dashboards->Browse, find the "awx-demo" and click. These should have graphs.
5. Now you can modify these and add panels for whichever metrics you like.
+
+### Alerts in Grafana
+
+We are configuring alerts in grafana using the provisioning files method. This feature is new in Grafana as of August, 2022. Documentation can be found: https://grafana.com/docs/grafana/latest/administration/provisioning/#alerting however it does not fully show all parameters to the config. One way to understand how to build rules is to build them in the UI and use chrometools to inspect the payload as you save the rules. It appears that the "data" portion of the payload for each rule is the same syntax as needed in the provisioning file config. To reload the alerts without restarting the container, from within the container you can send a POST with `curl -X POST http://admin:admin@localhost:3000/api/admin/provisioning/alerting/relo
+ad`. Keep in mind the grafana container does not default contain `curl` and you can get it with `apk add curl`.