Difference between revisions of "Edge Monitoring"
From RifidiWiki
(→Configuration) |
|||
| Line 11: | Line 11: | ||
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) | 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 rifidiserver.ini - A full list of Rifidi Edge configuartion parameters can be found Edge_Server_Configuration | ||
| − | |||
;-Dorg.rifidi.jolokia.enabled=true | ;-Dorg.rifidi.jolokia.enabled=true | ||
| + | Jolokia starts by default. | ||
;-Dorg.rifidi.jolokia.port=8091 | ;-Dorg.rifidi.jolokia.port=8091 | ||
| + | Jolokia port | ||
=Examples= | =Examples= | ||
Revision as of 15:42, 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 rifidiserver.ini - A full list of Rifidi Edge configuartion parameters can be found Edge_Server_Configuration
- -Dorg.rifidi.jolokia.enabled=true
Jolokia starts by default.
- -Dorg.rifidi.jolokia.port=8091
Jolokia port
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
