Difference between revisions of "Edge Monitoring"
From RifidiWiki
Line 1: | Line 1: | ||
− | Prior to Rifidi 3.1 (coming Fall 2014) Edge Monitoring is available through JMX/MBeans via RMI. Starting in 3.1 Edge Monitoring is now accessible though Resftful Services (leveraging [http://www.jolokia.org/ Jolokia plugin]. Jolokia exposes all JMX/Mbeans via | + | =Introduction= |
+ | Prior to Rifidi 3.1 (coming Fall 2014) Edge Monitoring is available through JMX/MBeans via RMI. Starting in 3.1 Edge Monitoring is now accessible though Resftful Services (leveraging [http://www.jolokia.org/ Jolokia plugin]. Jolokia exposes all JMX/Mbeans via Rest | ||
The types of components which can be monitored include | The types of components which can be monitored include | ||
Line 7: | Line 8: | ||
*Messaging | *Messaging | ||
+ | =Examples= | ||
Example calls are: | Example calls are: | ||
Revision as of 18:59, 24 September 2014
Introduction
Prior to Rifidi 3.1 (coming Fall 2014) Edge Monitoring is available through JMX/MBeans via RMI. Starting in 3.1 Edge Monitoring is now accessible though Resftful Services (leveraging Jolokia plugin. Jolokia exposes all JMX/Mbeans via Rest
The types of components which can be monitored include
- Java Virtual Machine (Memory, CPU etc..)
- Sensors/Readers (Status, Properties etc..)
- OSGI (Status, Applications etc..)
- Messaging
Examples
Example calls are:
- Java Virtual Machine HeapMemory Usage example URL - http://localhost:8080/jolokia/read/java.lang:type=Memory/HeapMemoryUsage/used
- To find all available MBeans list example URL - http://localhost:8080/jolokia/search/*,*
Additional features can be found on Jolokia Get/Post Features