The LifeKeeper API for Monitoring can obtain the operational status of LifeKeeper nodes and their protected resources by making status inquiries to the available nodes in the LifeKeeper cluster.


This document describes the LifeKeeper API for Monitoring (hereinafter referred to as the API) and is targeted for developers who manage the resource protected by LifeKeeper.

By using the API, the information supplied by the lcdstatus command is obtained through CGI script and the lighttpd module. By using this API, users can determine the current status of the LifeKeeper nodes and resources without logging-in to LifeKeeper servers.

The API can supply the following information.

    • LifeKeeper node status is the node alive and processing or down
    • Communication path status between nodes in the cluster, are communication path(s) up or down
    • Status of protected resources

To get the detailed status of any abnormal condition requires logging-in to LifeKeeper GUI or checking the LifeKeeper log as necessary.

  Chart 1. Overview of the LifeKeeper API for Monitoring

Information to be supplied with this API

The following information is supplied through this API when the user makes an inquiry to an active LifeKeeper node. The information supplied is about the specific LifeKeeper server to which the inquiry was directed even if the cluster consists of multiple servers.

    • Status
    • Operating status of each server
    • Node name
    • Operational status (ALIVE/DEAD)
    • Operational status of communication path(s)
    • Node name
    • Operational status (ALIVE/DEAD)
    • Address / device name
    • Status of protected resources
    • Node Name
    • Tag
    • Status (ISP, OSU, OSF, …)
    • Dependency setting
    • Mirror information for Data Replication resources (available only if status is ISP)
    • Replication status (75%, 100%, …)
    • Mirror status (Sync/Async, Paused, …)
    • Log
    • /var/log/lifekeeper.log
    • Up to 1000 lines (when data output format is HTML)
    • All (when data output format is plain text)
    • Not supported if log file path is changed
    • /var/log/lifekeeper.err
    • Up to 1000 lines (when data output format is HTML)
    • All (when data output format is plain text
    • Not supported if log file path is changed

Communication format

The API uses HTTP to obtain the requested information. To obtain information, the user sends a HTTP GET request to the CGI scripts via lighttpd on the specific server.

Data format

The following 3 data formats are available.

    • JSON
    • To be used by an external tool to analyze the status information returned
    • Status checking is possible
    • Log output is not available
    • HTML
    • To be used to visually check via a browser
    • Status checking is possible
    • Log information is available up to 1000 lines
    • plain text
    • Used for regular log checking
    • For logging purpose only and not for checking the status
    • All contents of /var/log/lifekeeper.log and /var/log/lifekeeper.err are available

Available JSON format from the status in figure 2 is shown in figure 3, and HTML format is in figure 4

Figure 2. Example of active LifeKeeper configuration

{ “resource”: [ { “replication”: {}, “child”: [ { “tag”: “datarep-data” } ], “server”: { “status”: “ISP”, “name”: “lk01” }, “tag”: “/data” }, { “replication”: { “percent”: “100%”, “mirror”: “Fully Operational” }, “child”: [], “server”: { “status”: “ISP”, “name”: “lk01” }, “tag”: “datarep-data” }, { “replication”: {}, “child”: [], “server”: { “status”: “ISP”, “name”: “lk01” }, “tag”: “ip-” } ], “compath”: [ { “status”: “ALIVE”, “server”: [ { “name”: “lk01”, “term”: “” }, { “name”: “lk02”, “term”: “” } ] }, { “status”: “ALIVE”, “server”: [ { “name”: “lk01”, “term”: “” }, { “name”: “lk02”, “term”: “” } ] } ], “server”: [ { “status”: “ALIVE”, “name”: “lk01” }, { “status”: “ALIVE”, “name”: “lk02” } ]


Figure 3. Status output example using the JSON data format

Figure 4. Status output using the HTML format

How to use

Activate the API

The API is disabled by default. To activate, requires modification of /etc/default/LifeKeeper set the LKAPI_MONITORING configuration parameter to true (see figure 5). Setting of the configuration parameter only activates the API on that node and therefore must be set on each node on which the API will be used. Setting of this configuration parameter does not require a restart of LifeKeeper..

Figure 5. Enabling the LifeKeeper API for Monitoring

Port number

The API uses port 779 by default. To change the port number, the user needs to set the following in /etc/default/LifeKeeper.

Figure 6. Change the port number for LifeKeeper API for Monitoring

Usage examples

To obtain information a request is made to a server with an active LifeKeeper API configuration. Basic example using curl.

curl http://<IPADDR>:779/Monitoring.cgi

If no arguments are given, the current status is obtained using the JSON data format.

Request for log information using HTML data format.

curl http://<IPADDR>:779/Monitoring.cgi?format=html&show=log

The list of available arguments can be found in the table below.

List 1. Arguments


All the users requesting information via the API must be authorized to get LifeKeeper status information.

For this reason, user security settings can limit the users who can get the status by, configuring SSL, and encrypting the information.

Basic Authentication

To obtain the information via the API, Basic Authentication is required. To setup the authentication requires modification to the lighttpd configuration file (Modify the part in red colored character.) plus a restart of the lighttpd module. See figure 7 for how to configure lightttp.conf.

After modification execute the command ”/opt/LifeKeeper/sbin/sv restart steeleye-lighttpd” and reboot lighttpd to restart lighttpd using the new configuration.

Figure 7. Basic Authentication setting example

SSL/TLS set up

SSL/TLS is available for the communication via this API. The lighttpd modifications for SSL/TLS is shown in the example in Figure 8. After modification execute the command ”/opt/LifeKeeper/sbin/sv restart steeleye-lighttpd” and reboot lighttpd to restart lighttpd with the new configuration.

Figure 8 SSL/TLS setting example

Modification to support SSL/TLS + Basic authentication

Using SSL/TLS, modification example to set up Basic authentication is below. After modification, execute the command “/opt/LifeKeeper/sbin/sv restart steeleye-lighttpd“ and restart lighttpd to reflect the modified set up.

Figure 9. SSL/TLS+Basic Authentication set up example

IP address access limitation

The lightppd configuration can also be setup to limit IP addresses that can be used to access data via the API. The lighttpd configuration to limit access is shown in Figure 9. The example will reject the connections from IP address other than After modification execute the command ”/opt/LifeKeeper/sbin/sv restart steeleye-lighttpd” to restart lighttpd with the new configuration.

Figure 10. IP access limit setting example


Errors can occur during the usage of this API when enabled. Should this occur, the summary of the error is output. Error example when JSON format is shown below.

HTTP status code returned by lighttpd is not described here.

Figure 11. Error output example

Similar message is output in the case the output format is HTML.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment