JMX monitoring and management of endpoints
------------------------------------------
Key: SYNAPSE-465
URL: https://issues.apache.org/jira/browse/SYNAPSE-465
Project: Synapse
Issue Type: Improvement
Components: Endpoints
Affects Versions: 1.2
Reporter: Eric Hubert
Assignee: Asankha C. Perera
Fix For: 1.3
* Ability to query status of endpoints via JMX
It must be possible to query the status (active/inactive) of endpoints via JMX.
While for single endpoints it is sufficient to have a state information
("active", "inactive") for load balancing groups the total number of endpoints
is needed to have the information about the total number of configured
endpoints, as well as the number of active endpoints.
* It must be possible to manually activate/deactivate endpoints via JMX
It must be possible to manually active/deactivate members of a load balancing
group via JMX. Manually deactivated nodes must not be activated automatically.
They need to be reactivated via JMX. This deactivation must not break requests
which are currently processed. This is required to put endpoints into
maintenence
* Read JMX statistics directly from memory
All JMX functions must read the statistics values directly from memory. It
should be possible to reset statistics on a leaf level (per endpoint) or on a
group level (all endpoints) or globally via a JMX operation from an external
monitoring application after data retrieval. JMS statistic gathering must be
decoupled from statistic recording to a database.
* Calculate and expose message throughput
Depending on message count and the configured collecting time interval, the
message throughput (in messages per second) has to be offered as an additional
queryable value.
* Expose message size metrics
If the implementation does not add a measurable performance overhead, within
the specified collection interval, minimum, maximum, average and total
cumulated message sizes as well as message size throughput in bytes per second
should be exposed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
