Hi Eric, Apparently we have inconsistent behavior between the different datasources. The format of the timestamp should be '%Y-%m-%dT%H:%M:%SZ' as defined in [1]. We need to go over the code and make sure all datasources are aligned. I created a bug for it [2]. [1] https://github.com/openstack/vitrage/blob/master/vitrage/datasources/transformer_base.py [2] https://bugs.launchpad.net/vitrage/+bug/1776181 Best regards, Ifat ---------- Forwarded message --------- From: Eric K <ekcs.openstack at gmail.com<mailto:ekcs.openstack at gmail.com>> Date: Sat, 9 Jun 2018 at 00:20 Subject: [openstack-dev] [vitrage] update_timestamp precision To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>> Hi I'm building integration with Vitrage webhook and looking for some clarification on the timestamp precision to expect. In the sample webhook payload found in doc the resource and the alarm shows different time stamp precisions: https://docs.openstack.org/vitrage/latest/contributor/notifier-webhook-plug in.html Thank you! __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180611/c4209605/attachment.html>