Releases: rabbitmq/omq
Releases · rabbitmq/omq
v0.9.0
v0.8.1
v0.8.0
Changelog
- 40d3734 Add rates to the final metrics
- da24f87 Bring back conumption by priority
- c4fd180 Bring back support for global metric labels
- 3177118 Bump github.com/Azure/go-amqp from 1.0.5 to 1.1.0 (#30)
- ec96476 Bump github.com/prometheus/client_golang from 1.19.1 to 1.20.2 (#29)
- 4f96b23 Handle context cancellation in AMQP consumer
- d2e2ff9 Redesigned metrics (#32)
v0.7.4
v0.7.3
v0.7.2
v0.7.1
Changelog
- Add
--spread-connections
(default: true) to distribute publisher and consumer connections between the available URIs
v0.7.0
Changelog
--publisher-uri
and--consumer-uri
can now be repeated to provide multiple endpoints- publishers and consumers will try all endpoints in a loop until a successful connection
- if a connection is lost, the next endpoint is tried
--amqp-send-settled
was added to publish pre-settled messages over AMQP; this results in a much higher publishing rate, sinceomq
doesn't wait before publishing the next message--log-out-of-order-messages
was added to log (and count in a metric) situations where the received message is older then the previously received message; this will happen when priorities are used or when messages are requeuedpriority
label was added toomq_messages_consumed_total
so consumption by priority can be monitored- end-to-end latency metric is a summary again, rather than a histogram (this may lead to performance issues in some situations with very high consumption rate; to be investigated in the future)
- Use
--log-level
(or-l
) to set debug/info/error log level;OMQ_LOG_LEVEL
does not do anything anymore - updated dashboard