Lighttpd
Rapport de recherche Datadog : Bilan sur l'adoption de l'informatique sans serveur Rapport : Bilan sur l'adoption de l'informatique sans serveur

Lighttpd

Agent Check Check de l'Agent

Supported OS: Linux Mac OS Windows

Dashboard lighttpd

Présentation

Le check lighttpd de l’Agent surveille la disponibilité, les octets traités, les requêtes par seconde, les codes de réponse et bien plus encore.

Configuration

Installation

Le check lighttpd est inclus avec le paquet de l’Agent Datadog : vous n’avez donc rien d’autre à installer sur vos serveurs lighttpd.

En outre, vous pouvez installer mod_status sur vos serveurs lighttpd.

Configuration

Host

Suivez les instructions ci-dessous pour configurer ce check lorsque l’Agent est exécuté sur un host. Consultez la section Environnement conteneurisé pour en savoir plus sur les environnements conteneurisés.

  1. Modifiez le fichier lighttpd.d/conf.yaml dans le dossier conf.d/ à la racine du répertoire de configuration de votre Agent. Consultez le fichier d’exemple lighttpd.d/conf.yaml pour découvrir toutes les options de configuration disponibles.

    init_config:
    
    instances:
     ## @param lighttpd_status_url - string - required
     ## Status url of your Lighttpd server.
     #
     - lighttpd_status_url: http://localhost/server-status?auto
  2. Redémarrez l’Agent.

Environnement conteneurisé

Consultez la documentation relative aux modèles d’intégration Autodiscovery pour découvrir comment appliquer les paramètres ci-dessous à un environnement conteneurisé.

ParamètreValeur
<NOM_INTÉGRATION>lighttpd
<CONFIG_INIT>vide ou {}
<CONFIG_INSTANCE>{"lighttpd_status_url": "http://%%host%%/server-status?auto"}

Validation

Lancez la sous-commande status de l’Agent et cherchez lighttpd dans la section Checks.

Données collectées

Métriques

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

Événements

Le check lighttpd n’inclut aucun événement.

Checks de service

- lighttpd.can_connect :

Renvoie CRITICAL si l’Agent ne parvient pas à se connecter à lighttpd pour recueillir des métriques. Si ce n’est pas le cas, renvoie OK.

Dépannage

Besoin d’aide ? Contactez l’assistance Datadog.

Pour aller plus loin

Pour mieux comprendre comment (ou pourquoi) surveiller les métriques de serveur web lighttpd avec Datadog, lisez nos articles de blog à ce sujet.