Difference between revisions of "Edge Monitoring"
From RifidiWiki
(→Examples) |
|||
| Line 7: | Line 7: | ||
*OSGI (Status, Applications etc..) | *OSGI (Status, Applications etc..) | ||
*Messaging | *Messaging | ||
| + | |||
| + | =Configuration= | ||
| + | |||
| + | Note: Default port changed from 8080 to 8091 in Rifidi 3.1.1 (as 8080 is a popular port used by other web servers such as Tomcat) | ||
| + | |||
| + | In rifidi | ||
| + | ;-Dorg.rifidi.jolokia.enabled=true | ||
| + | ;-Dorg.rifidi.jolokia.port=8091 | ||
=Examples= | =Examples= | ||
Example calls are: | Example calls are: | ||
| − | |||
*Java Virtual Machine HeapMemory Usage example URL - http://localhost:8091/jolokia/read/java.lang:type=Memory/HeapMemoryUsage/used | *Java Virtual Machine HeapMemory Usage example URL - http://localhost:8091/jolokia/read/java.lang:type=Memory/HeapMemoryUsage/used | ||
Revision as of 15:40, 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
Configuration
Note: Default port changed from 8080 to 8091 in Rifidi 3.1.1 (as 8080 is a popular port used by other web servers such as Tomcat)
In rifidi
- -Dorg.rifidi.jolokia.enabled=true
- -Dorg.rifidi.jolokia.port=8091
Examples
Example calls are:
- 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
