integrated Slack with monasca/grafana:4.0.0-1.5.0 and alarm definition like CPU_UTIL > 70, after crossing it triggers alarms as "CRITICAL" it collected properly in grafana & slack channel.
But after CPU utilisation become normal ( like 30 %) in grafana dashboard it became "normal" but in slack notification it hasn't passed that data. Here slack output when "STATE: ALARM"
maestropandy
commented
5 years ago
integrated Slack with monasca/grafana:4.0.0-1.5.0 and alarm definition like CPU_UTIL > 70, after crossing it triggers alarms as "CRITICAL" it collected properly in grafana & slack channel.
But after CPU utilisation become normal ( like 30 %) in grafana dashboard it became "normal" but in slack notification it hasn't passed that data. Here slack output when "STATE: ALARM"
{ "metrics": [ { "dimensions": { "zone": "nova", "service": "compute", "resource_id": "f12401cf-0a49-4cf3-876b-805d92368197", "hostname": "Prakash_5555_cmp04", "component": "vm", "device": "vda" }, "name": "io.write_bytes_sec", "id": null }, { "dimensions": { "zone": "nova", "service": "compute", "resource_id": "f12401cf-0a49-4cf3-876b-805d92368197", "hostname": "Prakash_5555_cmp04", "component": "vm", "device": "vdb" }, "name": "io.write_bytes_sec", "id": null } ], "alarm_id": "49a53ff3-f843-4b9e-8379-86c28fae35a0", "state": "ALARM", "alarm_timestamp": 1537272872, "tenant_id": "3c52bd9e72f04d40a4e0989f1463e3d8", "old_state": "OK", "alarm_description": "", "message": "Thresholds were exceeded for the sub-alarms: max(io.write_bytes_sec) > 10000.0 with the values: [7289972.398247574]", "alarm_definition_id": "88646b65-080c-4629-92a7-1b80647b83ad", "alarm_name": "io.Write_Madhan_Max" }