f24bed66a0
this does nothing. the listener currently consumes events across all queues, drops them into an 'incoming' queue. from here, a thread batches them based on batch options. the batched messages themselves are still in order and therefore sorting it does nothing. the only reason it'd be out of order is if a message was requeue'd. in this case, sorting will probably do nothing since the requeue'd location is probably not remotely close to original ordering and will probably never be batched with same messages to sort correctly. Change-Id: I6faa97bb90bee00ec94f4faf622822ea93655efb
Ceilometer
Ceilometer is a data collection service that collects event and metering data by monitoring notifications sent from OpenStack services. It publishes collected data to various targets including data stores and message queues.
Ceilometer is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Release notes are available at https://releases.openstack.org/teams/telemetry.html
Developer documentation is available at https://docs.openstack.org/ceilometer/latest/
For information on how to contribute to ceilometer, see the CONTRIBUTING.rst file.
The project home is at https://launchpad.net/ceilometer
To report any ceilometer related bugs, see https://bugs.launchpad.net/ceilometer/