Seems that this problem appear because of usage Elasticsearch, as there
is no such problem running devstack with Neutron and Ceilometer with
both publishers (rpc, upd). I'm not sure where this should be fixed as
in basic case everything works fine.
** Changed in: neutron
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1372792
Title:
Inconsistent timestamp formats in ceilometer metering messages
Status in OpenStack Neutron (virtual network service):
Opinion
Bug description:
The messages generated by neutron-metering-agent contain timestamps in
a different format than the other messages received through UDP from
ceilometer-agent-notification. This creates unnecessary troubles for
whoever is trying to decode the messages and do something useful with
them.
I particular, up to now, I found out about the timestamp field in the
bandwidth message.
They contain UTC dates (I hope), but there is no Z at the end, and
they contain a space instead of a T between date and time. In short,
they are not in ISO8601 as the timestamps in the other messages. I
found out about them because elasticsearch tries to parse them and
fails, throwing away the message.
This bug was filed against Ceilometer, but I have been redirected here:
https://bugs.launchpad.net/ceilometer/+bug/1370607
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1372792/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
