Inconsistent timestamp formats in ceilometer messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Vincent Hou |
Bug Description
The messages generated by cinder-
I particular, up to now, I found out about these fields:
- timestamp in volume and volume.size messages
- resource_
- resource_
- resource_
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 has been reported against Ceilometer, but I have been redirected here:
https:/
Changed in cinder: | |
milestone: | none → kilo-1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-1 → 2015.1.0 |
Interesting.
I will take a look.