Timestamp deduced alarm is in UTC

Asked by Walter Van Elshocht

Alarms received from Zabbix are in UTC+2 for example while the Vitrage deduced alarms are in the UTC time

2018-05-09 14:19:24.584 3463 INFO vitrage.notifier.service [-] Vitrage Event Info: event_type vitrage.deduced_alarm.deactivate
2018-05-09 14:19:24.584 3463 INFO vitrage.notifier.service [-] Vitrage Event Info: metadata {'timestamp': u'2018-05-09 12:19:24.582159', 'message_id': u'b4e6cc0c-f579-4f57-86ef-e7e13e0f6a2b'}
2018-05-09 14:19:24.584 3463 INFO vitrage.notifier.service [-] Vitrage Event Info: payload {u'is_placeholder': False, u'vitrage_id': u'ALARM:vitrage:CPU performance degradation:RESOURCE:nova.instance:4d14316c-7c33-4209-b1cf-12246198cda0', u'is_deleted': True, u'name': u'CPU performance degradation', u'update_timestamp': u'2018-05-09T12:19:24Z', u'sample_timestamp': u'2018-05-09 12:19:24.580963+00:00', u'state': u'Inactive', u'operational_severity': u'WARNING', u'aggregated_severity': u'WARNING', u'category': u'ALARM', u'type': u'vitrage', u'severity': u'warning'}

When a list of alarms is requested in the Horizon GUI, alarms from zabbix will show the local zone time f.e 14:19:...... while the deduced alarms will show the UTC time zone f.e. 12:19:....

How can this be corrected?

Question information

Language:
English Edit question
Status:
Expired
For:
Vitrage Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.