You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (Jira)" <ji...@apache.org> on 2021/03/16 13:09:00 UTC
[jira] [Updated] (ARTEMIS-3175) Restrict/truncate messages
attributes to a configurable limit for management views
[ https://issues.apache.org/jira/browse/ARTEMIS-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully updated ARTEMIS-3175:
--------------------------------
Description:
We still populate lots of per message data. ARTEMIS-3141 limits the number of messages that are returned by default however the message data is still displayed in full.
With a few kbytes of data in message properties, it can quickly get become a burden.
The open type message body is called BodyPreview - but we put the whole body in there at the moment.
This enhancement will add an address setting - *_management-message-attribute-size-limit_*
with a reasonable 256 default.
That will truncate all message attributes returned in JSON or JMX OpenData to this value.
Most properties will fit in that limit and be fully visible, anything bigger will be difficult to view and is too much data to be exposing in bulk to a console or client.
was:
We still populate lots of per message data. ARTEMIS-3141 limits the number of messages that are returned by default however the message data is still displayed in full.
With a few kbytes of data in message properties, it can quickly get become a burden.
The open type message body is called BodyPreview - but we put the whole body in there at the moment.
This enhancement will add an address setting - *_managementMessageAttributeSizeLimit_*
with a reasonable 256 default.
That will truncate all message attributes returned in JSON or JMX OpenData to this value.
Most properties will fit in that limit and be fully visible, anything bigger will be difficult to view and is too much data to be exposing in bulk to a console or client.
> Restrict/truncate messages attributes to a configurable limit for management views
> ----------------------------------------------------------------------------------
>
> Key: ARTEMIS-3175
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3175
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 2.17.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> We still populate lots of per message data. ARTEMIS-3141 limits the number of messages that are returned by default however the message data is still displayed in full.
> With a few kbytes of data in message properties, it can quickly get become a burden.
> The open type message body is called BodyPreview - but we put the whole body in there at the moment.
> This enhancement will add an address setting - *_management-message-attribute-size-limit_*
> with a reasonable 256 default.
> That will truncate all message attributes returned in JSON or JMX OpenData to this value.
> Most properties will fit in that limit and be fully visible, anything bigger will be difficult to view and is too much data to be exposing in bulk to a console or client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)