Lighttpd

문서 > 통합 > Lighttpd

Supported OS Linux Windows Mac OS

통합 버전5.0.0

이 페이지는 아직 한국어로 제공되지 않으며 번역 작업 중입니다. 번역에 관한 질문이나 의견이 있으시면 언제든지 저희에게 연락해 주십시오.

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 included in the Datadog Agent package, so you don’t need to install anything else on your Lighttpd servers.

In addition, install mod_status on your Lighttpd servers.

Configuration

Host

To configure this check for an Agent running on a host:

Edit the lighttpd.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory. See the sample lighttpd.d/conf.yaml for all available configuration options:

init_config:

instances:
  ## @param lighttpd_status_url - string - required
  ## Status url of your Lighttpd server.
  #
  - lighttpd_status_url: http://localhost/server-status?auto

Restart the Agent.

Containerized

For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.

Parameter	Value
`<INTEGRATION_NAME>`	`lighttpd`
`<INIT_CONFIG>`	blank or `{}`
`<INSTANCE_CONFIG>`	`{"lighttpd_status_url": "http://%%host%%/server-status?auto"}`

Log collection

Collecting logs is disabled by default in the Datadog Agent, you need to enable it in datadog.yaml:
```
logs_enabled: true
```
Add this configuration block to your lighttpd.d/conf.yaml file to start collecting your lighttpd Logs:
```
logs:
  - type: file
    path: /path/to/my/directory/file.log
    source: lighttpd
```
Change the path parameter value and configure it for your environment. See the sample lighttpd.d/conf.yaml for all available configuration options.
Restart the Agent.

Validation

Run the Agent’s status subcommand and look for lighttpd under the Checks section.

Data Collected

Metrics

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_keep_alive (gauge)	[Lighttpd 2 only] The number of idle connections. 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_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_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.net.bytes (gauge)	[Lighttpd 1 only] The number of bytes sent and received since start. Shown as byte
lighttpd.net.bytes_in (rate)	[Lighttpd 2 only] The number of bytes received per second. 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 (rate)	[Lighttpd 2 only] The number of bytes sent per second. Shown as byte
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_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_per_s (gauge)	[Lighttpd 1 only] The number of bytes sent and 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.connections_total (rate)	[Lighttpd 2 only] The total number of connections per second. Shown as connection
lighttpd.net.hits (gauge)	[Lighttpd 1 only] The number of hits since start. Shown as hit
lighttpd.net.request_per_s (gauge)	[Lighttpd 1 only] The number of requests per second. 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_avg_5sec (gauge)	[Lighttpd 2 only] The average number of requests per second in the past 5 seconds. Shown as request
lighttpd.net.requests_total (rate)	[Lighttpd 2 only] The number of requests per second. Shown as request
lighttpd.performance.busy_servers (gauge)	[Lighttpd 1 only] The number of active connections. Shown as connection
lighttpd.performance.idle_server (gauge)	[Lighttpd 1 only] The number of idle connections. Shown as connection
lighttpd.performance.memory_usage (gauge)	[Lighttpd 2 only] The amount of memory used by the server. Shown as byte
lighttpd.performance.uptime (gauge)	[Lighttpd 1 only] The amount of time the server has been up and running. Shown as second
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 events.

Service Checks

lighttpd.can_connect
Returns CRITICAL if the Agent is unable to connect to and collect metrics from the monitored Lighttpd instance. Returns OK otherwise.
Statuses: ok, critical

Troubleshooting

Need help? Contact Datadog support.