[
https://issues.apache.org/jira/browse/QPID-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503523#comment-16503523
]
Robbie Gemmell commented on QPID-8204:
--------------------------------------
I took the use case to be, have a way of knowing what the max size received so
far actually is, so you could perhaps monitor the existing peak and either set
or adjust limits accordingly. For example, you have no explicit limit set, but
decided you want to only allow for current usage, now what should you set it
to? Or alternatively, your limit is currently set at 100MB but it seems actual
traffic is only at 1MB, so decide actually lets change the limit to 2MB).
Presumably you could use the old alerting to achieve that overview somewhat
also.
The name point is interesting. When I pointed out the two were different
earlier, I somewhat expected 'In' to be added to the Broker attribute rather
than removed from the Virtualhost one. "MaximumMessageSize" seems more like it
would set a limit than be an observed-peak. I forget what the actual attribute
to set the limit is :)
> [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]
