Supported OS Linux Windows Mac OS

Versión de la integración5.1.0

Dashboard de Lighttpd

Información general

El check de Lighttpd del Agent realiza un seguimiento del tiempo de actividad, de los bytes utilizados, de las solicitudes por segundo, de los códigos de respuesta y mucho más.

Configuración

Instalación

El check de Lighttpd está incluido en el paquete del Datadog Agent, por lo que no necesitas instalar nada más en tus servidores de Lighttpd.

Además, instala mod_status en tus servidores de Lighttpd.

Configuración

Host

Para configurar este check para un Agent que se ejecuta en un host:

  1. Edita el archivo lighttpd.d/conf.yaml, que se encuentra en la carpeta conf.d/ en la raíz del directorio de configuración del Agent. Para ver todas las opciones de configuración disponibles, consulta el ejemplo marathon.d/conf.yaml:

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

Contenedores

Para entornos en contenedores, consulta las plantillas de integración de Autodiscovery para obtener orientación sobre la aplicación de los parámetros que se indican a continuación.

ParámetroValor
<INTEGRATION_NAME>lighttpd
<INIT_CONFIG>en blanco o {}
<INSTANCE_CONFIG>{"lighttpd_status_url": "http://%%host%%/server-status?auto"}

Recopilación de logs

  1. La recopilación de logs se encuentra deshabilitada de manera predeterminada en el Datadog Agent; debes habilitarla en el archivo datadog.yaml:

    logs_enabled: true
    
  2. Añade este bloque de configuración a tu archivo lighttpd.d/conf.yaml para empezar a recopilar logs de Lighttpd:

    logs:
      - type: file
        path: /path/to/my/directory/file.log
        source: lighttpd
    

    Cambia el valor del parámetro path y configúralo para tu entorno. Para ver todas las opciones de configuración disponibles, consulta el ejemplo lighttpd.d/conf.yaml.

  3. Reinicia el Agent.

Validación

Ejecuta el subcomando status del Agent y busca lighttpd en la sección Checks.

Datos recopilados

Métricas

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

Eventos

El check de Lighttpd no incluye eventos.

Checks de servicio

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

Solucionar problemas

¿Necesitas ayuda? Ponte en contacto con el servicio de asistencia de Datadog.

Referencias adicionales

PREVIEWING: mcretzman/DOCS-10911-App-API-Pro-redirects-revise