Re: [wildfly-dev] Configuration of statistics gathering

For the messaging subsystem, we can capture message counters for queues[1]. Capturing the counters is controlled by the /subsystem=messaging/hornetq-server=* resources * message-counter-enabled attribute (default to false) controls whether the hornetq-server resource capture the counters * message-counter-sample-period attributecontrols the interval to capture the counters (default to 10s, only relevant if message-counter-enabled is true) * message-counter-max-day-history attributes controls how many days to keep the message counter history (default to 10 days, only relevant if message-counter-enabled is true) => if message-counter-enabled is true, message-counter-sample-period is short, and message-counter-max-day-history is big, the counters can eat up a significant chunk of memory. The hornetq-server resource has 2 operations to reset the counters and their histories: * reset-all-message-counter-histories * reset-all-message-counters The counters themselves can be fetched from the queue and jms-queue resources (children of the /subsystem=messaging/hornetq-server=* resource) with the operations: * list-message-counter-as-json * list-message-counter-as-html * list-message-counter-history-as-json * list-message-counter-history-as-html By default, nothing is enabled, nothing is gathered and there should be no performance or memory impact. [1] http://docs.jboss.org/hornetq/2.4.0.beta1/docs/user-manual/html_single/in... -- Jeff Mesnil JBoss, a division of Red Hat http://jmesnil.net/