Difference between revisions of "Edge Monitoring"
From RifidiWiki
(→Introduction=) |
(→Examples) |
||
Line 11: | Line 11: | ||
Example calls are: | Example calls are: | ||
− | + | Note: Default port changed from 8080 to 8091 in 3.1.1 (as 8080 is a popular port used by other web servers such as Tomcat) | |
− | *To find all available MBeans list example URL - http://localhost: | + | *Java Virtual Machine HeapMemory Usage example URL - http://localhost:8091/jolokia/read/java.lang:type=Memory/HeapMemoryUsage/used |
+ | |||
+ | *To find all available MBeans list example URL - http://localhost:8091/jolokia/search/*,* | ||
Additional features can be found on [http://www.jolokia.org/reference/html/protocol.html#request-response Jolokia Get/Post Features ] | Additional features can be found on [http://www.jolokia.org/reference/html/protocol.html#request-response Jolokia Get/Post Features ] |
Revision as of 15:22, 7 December 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:
Note: Default port changed from 8080 to 8091 in 3.1.1 (as 8080 is a popular port used by other web servers such as Tomcat)
- Java Virtual Machine HeapMemory Usage example URL - http://localhost:8091/jolokia/read/java.lang:type=Memory/HeapMemoryUsage/used
- To find all available MBeans list example URL - http://localhost:8091/jolokia/search/*,*
Additional features can be found on Jolokia Get/Post Features