Check système
Rapport de recherche Datadog : Bilan sur l'adoption de l'informatique sans serveur Rapport : Bilan sur l'adoption de l'informatique sans serveur

Check système

Agent Check Check de l'Agent

Supported OS: Linux Mac OS Windows

Présentation

Recueillez des métriques concernent le processeur, les E/S, la charge, la mémoire, le swap et l’uptime de votre système. Les checks suivants sont également liés au système :

  • Check de répertoire : enregistrez des métriques à partir des fichiers de répertoires donnés.
  • Check de disque : enregistrez des métriques sur vos disques.
  • Check de processus : enregistrez des métriques à partir d’un processus en cours d’exécution spécifique sur un système.

Implémentation

Installation

Le check système est inclus avec le paquet de l’Agent Datadog. Vous n’avez donc rien à installer sur votre serveur.

Données collectées

Métriques

system.cpu.guest
(gauge)
The percent of time the CPU spent running the virtual processor. Only applies to hypervisors.
Shown as percent
system.cpu.idle
(gauge)
Percent of time the CPU spent in an idle state.
Shown as percent
system.cpu.interrupt
(gauge)
The percentage of time that the processor is spending on handling Interrupts.
Shown as percent
system.cpu.iowait
(gauge)
The percent of time the CPU spent waiting for IO operations to complete.
Shown as percent
system.cpu.stolen
(gauge)
The percent of time the virtual CPU spent waiting for the hypervisor to service another virtual CPU. Only applies to virtual machines.
Shown as percent
system.cpu.system
(gauge)
The percent of time the CPU spent running the kernel.
Shown as percent
system.cpu.user
(gauge)
The percent of time the CPU spent running user space processes.
Shown as percent
system.fs.file_handles.allocated
(gauge)
Number of allocated file handles over the system.
Shown as file
system.fs.file_handles.allocated_unused
(gauge)
Number of allocated file handles unused over the system.
Shown as file
system.fs.file_handles.in_use
(gauge)
The amount of used allocated file handles over the system max.
Shown as fraction
system.fs.file_handles.max
(gauge)
Maximum of allocated files handles over the system
Shown as file
system.fs.file_handles.used
(gauge)
Number of allocated file handles used over the system.
Shown as file
system.fs.inodes.free
(gauge)
The number of free inodes.
Shown as inode
system.fs.inodes.in_use
(gauge)
The number of inodes in use as a fraction of the total.
Shown as fraction
system.fs.inodes.total
(gauge)
The total number of inodes.
Shown as inode
system.fs.inodes.used
(gauge)
The number of inodes in use.
Shown as inode
system.io.avg_q_sz
(gauge)
The average queue size of requests issued to the device.
Shown as request
system.io.avg_rq_sz
(gauge)
The average size of requests issued to the device (Linux only).
Shown as sector
system.io.await
(gauge)
The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them (Linux only).
Shown as millisecond
system.io.bytes_per_s
(gauge)
Byte transfer rate for this device (Datadog Agent v5 on Darwin-Mac only).
Shown as byte
system.io.r_await
(gauge)
The average time for read requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them (Linux only).
Shown as millisecond
system.io.r_s
(gauge)
The number of read requests issued to the device per second.
Shown as request
system.io.rkb_s
(gauge)
The number of kibibytes read from the device per second.
Shown as kibibyte
system.io.rrqm_s
(gauge)
The number of read requests merged per second that were queued to the device (Linux only).
Shown as request
system.io.svctm
(gauge)
The average service time for requests issued to the device (Linux only).
Shown as millisecond
system.io.util
(gauge)
The percent of CPU time during which I/O requests were issued to the device (Linux only).
Shown as percent
system.io.w_await
(gauge)
The average time for write requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them (Linux only).
Shown as millisecond
system.io.w_s
(gauge)
The number of write requests issued to the device per second.
Shown as request
system.io.wkb_s
(gauge)
The number of kibibytes written to the device per second.
Shown as kibibyte
system.io.wrqm_s
(gauge)
The number of write requests merged per second that were queued to the device (Linux only).
Shown as request
system.load.1
(gauge)
The average system load over one minute. (Linux only)
system.load.15
(gauge)
The average system load over fifteen minutes. (Linux only)
system.load.5
(gauge)
The average system load over five minutes. (Linux only)
system.load.norm.1
(gauge)
The average system load over one minute normalized by the number of CPUs. (Linux only)
system.load.norm.15
(gauge)
The average system load over fifteen minutes normalized by the number of CPUs. (Linux only)
system.load.norm.5
(gauge)
The average system load over five minutes normalized by the number of CPUs. (Linux only)
system.mem.buffered
(gauge)
The amount of physical RAM used for file buffers.
Shown as byte
system.mem.cached
(gauge)
The amount of physical RAM used as cache memory.
Shown as byte
system.mem.commit_limit
(gauge)
The total amount of memory currently available to be allocated on the system, based on the overcommit ratio. (Linux only)
Shown as byte
system.mem.committed
(gauge)
The amount of physical memory for which space has been reserved on the disk paging file in case it must be written back to disk.
Shown as byte
system.mem.committed_as
(gauge)
The amount of memory presently allocated on the system, even if it has not been "used" by processes as of yet. (Linux only)
Shown as byte
system.mem.free
(gauge)
The amount of free RAM.
Shown as byte
system.mem.nonpaged
(gauge)
The amount of physical memory used by the OS for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated.
Shown as byte
system.mem.page_free
(gauge)
The amount of the page file that's free. Used in Agent versions < 5.12 on Windows Agents.
Shown as byte
system.mem.page_pct_free
(gauge)
The amount of the page file in use as a fraction of the total. Used in Agent versions < 5.12 on Windows Agents.
Shown as fraction
system.mem.page_tables
(gauge)
The amount of memory dedicated to the lowest page table level. Used in Agent versions < 5.12 on Windows Agents.
Shown as byte
system.mem.page_total
(gauge)
The total size of the page file. Used in Agent versions < 5.12 on Windows Agents.
Shown as byte
system.mem.page_used
(gauge)
The amount of the page file in use. Used in Agent versions < 5.12 on Windows Agents.
Shown as byte
system.mem.paged
(gauge)
The amount of physical memory used by the OS for objects that can be written to disk when they are not in use.
Shown as byte
system.mem.pagefile.free
(gauge)
The amount of the page file that's free. Used from Agent version 5.12 to 6.0 (excluded) on Windows Agents.
Shown as byte
system.mem.pagefile.pct_free
(gauge)
The amount of the page file that's free as a fraction of the total. Used from Agent version 5.12 to 6.0 (excluded) on Windows Agents.
Shown as fraction
system.mem.pagefile.total
(gauge)
The total size of the page file.Used from Agent version 5.12 to 6.0 (excluded) on Windows Agents.
Shown as byte
system.mem.pagefile.used
(gauge)
The amount of the page file in use. Used from Agent version 5.12 to 6.0 (excluded) on Windows Agents.
Shown as byte
system.mem.pct_usable
(gauge)
The amount of usable physical RAM as a fraction of the total.
Shown as fraction
system.mem.shared
(gauge)
The amount of physical RAM used as shared memory.
Shown as byte
system.mem.slab
(gauge)
The amount of memory used by the kernel to cache data structures for its own use.
Shown as byte
system.mem.total
(gauge)
The total amount of physical RAM.
Shown as byte
system.mem.usable
(gauge)
Value of MemAvailable from /proc/meminfo if present, but falls back to adding free + buffered + cached memory if not.
Shown as byte
system.mem.used
(gauge)
The amount of RAM in use.
Shown as byte
system.proc.count
(gauge)
The number of processes. The Linux Proc Extras integration is required to capture this metric on a Linux-based system.
Shown as process
system.proc.queue_length
(gauge)
The number of threads that are observed as delayed in the processor ready queue and are waiting to be executed. The Linux Proc Extras integration is required to capture this metric on a Linux-based system.
Shown as thread
system.swap.cached
(gauge)
The amount of swap used as cache memory.
Shown as byte
system.swap.free
(gauge)
The amount of free swap space.
Shown as byte
system.swap.pct_free
(gauge)
The amount of swap space not in use as a fraction of the total.
Shown as fraction
system.swap.total
(gauge)
The total amount of swap space.
Shown as byte
system.swap.used
(gauge)
The amount of swap space in use.
Shown as byte
system.uptime
(gauge)
The amount of time the system has been working and available.
Shown as second

Événements

Le check système n’inclut aucun événement.

Checks de service

Le check système n’inclut aucun check de service.

Tags

Le tag host:<HOSTNAME> est automatiquement appliqué à l’ensemble des métriques système. En outre, le tag device:<NOM_APPAREIL> est appliqué aux espaces de nommage suivants :

  • system.disk.*
  • system.fs.inodes.*
  • system.io.*
  • system.net.*

System Core

Ce check recueille le nombre de cœurs du processeur sur un host ainsi que les temps processeur (système, utilisateur, inactivité, etc.).

Implémentation

Installation

Le check System Core est inclus avec le paquet de l’Agent Datadog. Vous n’avez donc rien à installer sur votre serveur.

Configuration

  1. Modifiez le fichier system_core.d/conf.yaml dans le dossier conf.d/ à la racine du répertoire de configuration de votre Agent. Consultez le fichier d’exemple system_core.d/conf.yaml pour découvrir toutes les options de configuration disponibles. Remarque : au moins une entrée est requise dans instances pour activer le check. Exemple :

      init_config:
      instances:
        - foo: bar
  2. Redémarrez l’Agent.

Validation

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

Données collectées

Métriques

system.core.count
(gauge)
The number of CPU cores on the host
Shown as core
system.core.user
(gauge)
A given core's user-space CPU time
system.core.system
(gauge)
A given core's system CPU time
system.core.idle
(gauge)
A given core's idle CPU time

Selon la plateforme, le check peut recueillir d’autres métriques de temps processeur, p. ex. system.core.interrupt sous Windows, system.core.iowait sous Linux, etc.

Événements

Le check System Core n’inclut aucun événement.

Checks de service

Le check System Core n’inclut aucun check de service.

System Swap

Ce check surveille le nombre d’octets entrants et sortants du swap sur le système.

Implémentation

Installation

Le check System Swap est inclus avec le paquet de l’Agent Datadog. Vous n’avez donc rien à installer sur votre serveur.

Configuration

  1. Modifiez le fichier system_swap.d/conf.yaml dans le dossier conf.d/ à la racine du répertoire de configuration de votre Agent. Consultez le fichier d’exemple system_swap.d/conf.yaml pour découvrir toutes les options de configuration disponibles. Remarque : aucune configuration initiale n’est possible pour ce check.

  2. Redémarrez l’Agent.

Validation

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

Données collectées

Métriques

system.swap.swapped_in
(gauge)
Bytes of memory swapped in
system.swap.swapped_out
(gauge)
Bytes of memory swapped out

Événements

Le check System Swap n’inclut aucun événement.

Checks de service

Le check System Swap n’inclut aucun check de service.