Hi Eric, The format of the vitrage_id was changed to UUID in Pike release. It appears that the API documentation [1] is outdated. I’ll fix it. The vitrage_id that you get in the webhook notification should match the one coming from ‘vitrage alarm list’. The ‘id’ field is determined by the external monitor, so it might be different.
Best Regards, Ifat ---------- Forwarded message --------- From: Eric K <ekcs.openst...@gmail.com<mailto:ekcs.openst...@gmail.com>> Date: Sat, 9 Jun 2018 at 01:40 Subject: [openstack-dev] [vitrage] matching webhook vs alarm list To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Hi I'm building integration with Vitrage webhook and looking for some clarification on what ID to use for matching a webhook notification to the specific alarm from the alarm list. In the sample alarm list response, there is an 'id' field and a 'vitrage_id' field [1], where as in the sample webhook notification payload, there is a 'vitrage_id' field [2]. I'd assume we can match by the 'vitrage_id', but the samples have very different formats for 'vitrage_id', so I just want to confirm. Thank you! [1] https://docs.openstack.org/vitrage/latest/contributor/vitrage-api.html#id22 [2] { "notification": "vitrage.alarm.activate", "payload": { "vitrage_id": "2def31e9-6d9f-4c16-b007-893caa806cd4", "resource": { "vitrage_id": "437f1f4c-ccce-40a4-ac62-1c2f1fd9f6ac", "name": "app-1-server-1-jz6qvznkmnif", "update_timestamp": "2018-01-22 10:00:34.327142+00:00", "vitrage_category": "RESOURCE", "vitrage_operational_state": "OK", "vitrage_type": "nova.instance", "project_id": "8f007e5ba0944e84baa6f2a4f2b5d03a", "id": "9b7d93b9-94ec-41e1-9cec-f28d4f8d702c" }, "update_timestamp": "2018-01-22T10:00:34Z", "vitrage_category": "ALARM", "state": "Active", "vitrage_type": "vitrage", "vitrage_operational_severity": "WARNING", "name": "Instance memory performance degraded" } } https://docs.openstack.org/vitrage/latest/contributor/notifier-webhook-plugin.html __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
