[
https://issues.apache.org/jira/browse/QPID-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503546#comment-16503546
]
Alex Rudyy commented on QPID-8204:
----------------------------------
Keith,
Robbie had identified the use case correctly.
The teams managing brokers need to understand what are the maximum sizes of
messages flowing through their brokers in order to adjust the max message size
limits or estimate peak loads in order to adjust memory settings.
Robbie,
I was considering adding 2 limits for inbound and outbound messages for
symmetry but realized that sizes of outbound messages are less important.
As for using {{HighWatermark}} in name, I am happy to change names of new stats
name to make names consistent through the broker.
> [Broker-J] Add statistics to report the maximum size of incoming messages
> -------------------------------------------------------------------------
>
> Key: QPID-8204
> URL: https://issues.apache.org/jira/browse/QPID-8204
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.5
>
>
> Add statistics to report the maximum size of incoming messages on Broker and
> Virtual Hosts. Add a switch to enable/disable collection of statistics for
> message maximum size . By default, collection of maximum size statistics
> should be disabled
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
