[
https://issues.apache.org/jira/browse/ARTEMIS-2636?focusedWorklogId=399775&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-399775
]
ASF GitHub Bot logged work on ARTEMIS-2636:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Mar/20 22:21
Start Date: 07/Mar/20 22:21
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #3005:
ARTEMIS-2636: Introduce Disk Usage Metrics
URL: https://github.com/apache/activemq-artemis/pull/3005#issuecomment-596143333
checking build histories of master on travis, seems as soon as PR #3003 was
merged, the build starting failing with the issue, as such does look like it is
related to PR #3003
here is the build on master straight after 3003 was merged
https://travis-ci.org/apache/activemq-artemis/builds/658977926?utm_source=github_status&utm_medium=notification
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 399775)
Time Spent: 2.5h (was: 2h 20m)
> Expose disk store used percentage metric
> ----------------------------------------
>
> Key: ARTEMIS-2636
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2636
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.11.0
> Reporter: Christoph Ewerlin
> Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> It would be very nice if the disk store used could be exposed via the metrics
> registry (preferably) and/or JMX like address.memory.usage already already is.
> In addition it would be nice to have percentage values for both
> address_memory_usage and disk_store_usage which would make setting up alarms
> much easier.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
