Datadog-Lighttpd Integration

Lighttpd Dashboard

Overview

The Agent’s lighttpd check tracks uptime, bytes served, requests per second, response codes, and more.

Setup

Installation

The lighttpd check is packaged with the Agent, so simply install the Agent on your lighttpd servers. If you need the newest version of the check, install the dd-check-lighttpd package.

You’ll also need to install mod_status on your Lighttpd servers.

Configuration

Create a file lighttpd.yaml in the Agent’s conf.d directory. See the sample lighttpd.yaml for all available configuration options:

init_config:

instances:
# Each instance needs a lighttpd_status_url. Tags are optional.
  - lighttpd_status_url: http://example.com/server-status?auto
#   tags:
#     - instance:foo

Restart the Agent to begin sending lighttpd metrics to Datadog.

Validation

Run the Agent’s info subcommand and look for lighttpd under the Checks section:

  Checks
  ======
    [...]

    lighttpd
    -------
      - instance #0 [OK]
      - Collected 30 metrics, 0 events & 1 service check

    [...]

Compatibility

The lighttpd check is compatible with all major platforms.

Data Collected

Metrics

lighttpd.net.bytes
(gauge)
[Lighttpd 1 only] The number of bytes sent and received since start.
shown as byte
lighttpd.net.hits
(gauge)
[Lighttpd 1 only] The number of hits since start.
shown as hit
lighttpd.net.bytes_per_s
(gauge)
[Lighttpd 1 only] The number of bytes sent and received per second.
shown as byte
lighttpd.net.request_per_s
(gauge)
[Lighttpd 1 only] The number of requests per second.
shown as request
lighttpd.performance.idle_server
(gauge)
[Lighttpd 1 only] The number of idle connections.
shown as connection
lighttpd.performance.busy_servers
(gauge)
[Lighttpd 1 only] The number of active connections.
shown as connection
lighttpd.performance.uptime
(gauge)
[Lighttpd 1 only] The amount of time the server has been up and running.
shown as second
lighttpd.connections.state_start
(gauge)
[Lighttpd 2 only] The number of active connections in the state of initializing the read-idle timer.
shown as connection
lighttpd.connections.state_read_header
(gauge)
[Lighttpd 2 only] The number of active connections in the state of reading the http request header.
shown as connection
lighttpd.connections.state_handle_request
(gauge)
[Lighttpd 2 only] The number of active connections in the state of handling the request internally.
shown as connection
lighttpd.connections.state_write_response
(gauge)
[Lighttpd 2 only] The number of active connections in the state of writing the response to the network.
shown as connection
lighttpd.connections.state_keep_alive
(gauge)
[Lighttpd 2 only] The number of idle connections.
shown as connection
lighttpd.net.bytes_out_avg
(gauge)
[Lighttpd 2 only] The average number of bytes sent per second since start.
shown as byte
lighttpd.net.bytes_in_avg
(gauge)
[Lighttpd 2 only] The average number of bytes received per second since start.
shown as byte
lighttpd.net.bytes_in_avg_5sec
(gauge)
[Lighttpd 2 only] The average number of bytes received per second in the past 5 seconds.
shown as byte
lighttpd.net.bytes_out_avg_5sec
(gauge)
[Lighttpd 2 only] The average number of bytes sent per second in the past 5 seconds.
shown as byte
lighttpd.net.bytes_out
(rate)
[Lighttpd 2 only] The number of bytes sent per second.
shown as byte
lighttpd.net.bytes_in
(rate)
[Lighttpd 2 only] The number of bytes received per second.
shown as byte
lighttpd.net.connections_avg
(gauge)
[Lighttpd 2 only] The average number of connections per second since start.
shown as connection
lighttpd.net.connections_avg_5sec
(gauge)
[Lighttpd 2 only] The average number of connections per second in the past 5 seconds.
shown as connection
lighttpd.net.requests_avg_5sec
(gauge)
[Lighttpd 2 only] The average number of requests per second in the past 5 seconds.
shown as request
lighttpd.net.requests_avg
(gauge)
[Lighttpd 2 only] The average number of requests per second since start.
shown as request
lighttpd.net.requests_total
(rate)
[Lighttpd 2 only] The number of requests per second.
shown as request
lighttpd.net.connections_total
(rate)
[Lighttpd 2 only] The total number of connections per second.
shown as connection
lighttpd.performance.memory_usage
(gauge)
[Lighttpd 2 only] The amount of memory used by the server.
shown as byte
lighttpd.response.status_1xx
(rate)
[Lighttpd 2 only] The number of 1xx status codes generated per second.
shown as response
lighttpd.response.status_2xx
(rate)
[Lighttpd 2 only] The number of 2xx status codes generated per second.
shown as response
lighttpd.response.status_3xx
(rate)
[Lighttpd 2 only] The number of 3xx status codes generated per second.
shown as response
lighttpd.response.status_4xx
(rate)
[Lighttpd 2 only] The number of 4xx status codes generated per second.
shown as response
lighttpd.response.status_5xx
(rate)
[Lighttpd 2 only] The number of 5xx status codes generated per second.
shown as response

Events

The Lighttpd check does not include any event at this time.

Service Checks

- lighttpd.can_connect:

Returns CRITICAL if the Agent cannot connect to lighttpd to collect metrics, otherwise OK.

Troubleshooting

If you have any questions about Datadog or a use case our Docs didn’t mention, we’d love to help! Here’s how you can reach out to us:

Visit the Knowledge Base

Learn more about what you can do in Datadog on the Support Knowledge Base.

Web Support

Messages in the event stream containing @support-datadog will reach our Support Team. This is a convenient channel for referencing graph snapshots or a particular event. In addition, we have a livechat service available during the day (EST) from any page within the app.

By Email

You can also contact our Support Team via email at support@datadoghq.com.

Over Slack

Reach out to our team and other Datadog users on Slack.

Further Reading

To get a better idea of how (or why) to monitor Lighttpd web server metrics with Datadog, check out our series of blog posts about it.