Bleemeo agent can relay your custom metrics to Bleemeo Cloud platform. Several ways to gather custom metrics exists:
Bleemeo agent could check that your custom application is alive. It could use built-in check (HTTP and TCP) or any Nagios check command.
To configure additional check, add the following to your Bleemeo agent
service:- id: "myapplication"port: 8080check_type: "nagios"check_command: "command-to-run"- id: "custom_webserver"port: 8181check_type: "http"
Custom check are defined under
service in the configuration.
Add to your configuration file (any
*.conf file in
service:# Use "/path/to/bin --with-option" to check the service. Also keep a# TCP connection with 127.0.0.1:8080, if that connection is closed run# a check immediatly instead of waiting 1 minute.- id: "service_name"port: 8080address: "127.0.0.1"check_type: "nagios"check_command: "/path/to/bin --with-option"# HTTPS check to URL https://127.0.0.1:8443/check/- id: "an_https_server"port: 8443check_type: "https"http_path: "/check/"# TCP check on 127.0.0.1:22- id: "another_service"port: 22
Custom checks are run every minutes. If
port is provided, Bleemeo Agent
maintains a TCP connection with this port, and if that connection is closed
the check is run immediately.
id: Name of your service. This name must be unique for one Bleemeo Agent.
port: TCP port number. This field is mandatory if
check_type is not
address: IP address associated with the TCP port. Default value is "127.0.0.1".
check_type: Check used for this service. Possible value are:
check_commandto test liveliness of service.
http_path: The path of URL checked with HTTP or HTTPS
value is "/"
http_status_code: The expected status code of HTTP response (only valid if
is HTTP or HTTPS). Default is unset.
When set, the check pass if the response status code is equal to the expected one and critical in other case.
When unset, if response status code is
check_command: Command used for a Nagios check. This field is mandatory if
check_type is "nagios".
The command must conform to Nagios check standard, that is:
In addition, the command may print to stdout a short explanation of its result. For example if a check fail to connect to your service, the check may print: "CRITICAL - connection refused"