此内容没有您所选择的语言版本。
Chapter 225. Nagios Component
Available as of Camel version 2.3
The Nagios component allows you to send passive checks to Nagios.
Maven users will need to add the following dependency to their pom.xml
for this component:
225.1. URI format 复制链接链接已复制到粘贴板!
nagios://host[:port][?Options]
nagios://host[:port][?Options]
Camel provides two abilities with the Nagios component. You can send passive check messages by sending a message to its endpoint.
Camel also provides a EventNotifer which allows you to send notifications to Nagios.
225.2. Options 复制链接链接已复制到粘贴板!
The Nagios component supports 2 options which are listed below.
Name | Description | Default | Type |
---|---|---|---|
configuration (advanced) | To use a shared NagiosConfiguration | NagiosConfiguration | |
resolveProperty Placeholders (advanced) | Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. | true | boolean |
The Nagios endpoint is configured using URI syntax:
nagios:host:port
nagios:host:port
with the following path and query parameters:
225.2.1. Path Parameters (2 parameters): 复制链接链接已复制到粘贴板!
Name | Description | Default | Type |
---|---|---|---|
host | Required This is the address of the Nagios host where checks should be send. | String | |
port | Required The port number of the host. | int |
225.2.2. Query Parameters (7 parameters): 复制链接链接已复制到粘贴板!
Name | Description | Default | Type |
---|---|---|---|
connectionTimeout (producer) | Connection timeout in millis. | 5000 | int |
sendSync (producer) | Whether or not to use synchronous when sending a passive check. Setting it to false will allow Camel to continue routing the message and the passive check message will be send asynchronously. | true | boolean |
timeout (producer) | Sending timeout in millis. | 5000 | int |
synchronous (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean |
encryption (security) | To specify an encryption method. | Encryption | |
encryptionMethod (security) | Deprecated To specify an encryption method. | NagiosEncryptionMethod | |
password (security) | Password to be authenticated when sending checks to Nagios. | String |
225.3. Sending message examples 复制链接链接已复制到粘贴板!
You can send a message to Nagios where the message payload contains the message. By default it will be OK
level and use the CamelContext name as the service name. You can overrule these values using headers as shown above.
For example we send the Hello Nagios
message to Nagios as follows:
template.sendBody("direct:start", "Hello Nagios"); from("direct:start").to("nagios:127.0.0.1:5667?password=secret").to("mock:result");
template.sendBody("direct:start", "Hello Nagios");
from("direct:start").to("nagios:127.0.0.1:5667?password=secret").to("mock:result");
To send a CRITICAL
message you can send the headers such as:
Map headers = new HashMap(); headers.put(NagiosConstants.LEVEL, "CRITICAL"); headers.put(NagiosConstants.HOST_NAME, "myHost"); headers.put(NagiosConstants.SERVICE_NAME, "myService"); template.sendBodyAndHeaders("direct:start", "Hello Nagios", headers);
Map headers = new HashMap();
headers.put(NagiosConstants.LEVEL, "CRITICAL");
headers.put(NagiosConstants.HOST_NAME, "myHost");
headers.put(NagiosConstants.SERVICE_NAME, "myService");
template.sendBodyAndHeaders("direct:start", "Hello Nagios", headers);
225.4. Using NagiosEventNotifer 复制链接链接已复制到粘贴板!
The Nagios component also provides an EventNotifer which you can use to send events to Nagios. For example we can enable this from Java as follows:
In Spring XML its just a matter of defining a Spring bean with the type EventNotifier
and Camel will pick it up as documented here: Advanced configuration of CamelContext using Spring.
225.5. See Also 复制链接链接已复制到粘贴板!
- Configuring Camel
- Component
- Endpoint
- Getting Started