--- title: Systemd description: Get metrics about Systemd and units managed by Systemd breadcrumbs: Docs > Integrations > Systemd --- # Systemd Supported OS Integration version1.0.0 ## Overview{% #overview %} This check monitors [Systemd](https://www.freedesktop.org/wiki/Software/systemd/) and the units it manages through the Datadog Agent. - Track the state and health of your Systemd - Monitor the units, services, sockets managed by Systemd ## Setup{% #setup %} ### Installation{% #installation %} The Systemd check is included in the [Datadog Agent](https://app.datadoghq.com/account/settings/agent/latest) package. No additional installation is needed on your server. ### Configuration{% #configuration %} {% tab title="Host" %} #### Host{% #host %} To configure this check for an Agent running on a host: 1. Edit the `systemd.d/conf.yaml` file, in the `conf.d/` folder at the root of your Agent's configuration directory to start collecting your systemd performance data. See the [sample systemd.d/conf.yaml](https://github.com/DataDog/datadog-agent/blob/master/cmd/agent/dist/conf.d/systemd.d/conf.yaml.example) for all available configuration options. 1. [Restart the Agent](https://docs.datadoghq.com/agent/guide/agent-commands.md#start-stop-restart-the-agent). {% /tab %} {% tab title="Containerized" %} #### Containerized{% #containerized %} For containerized environments, mount the `/run/systemd/` folder, which contains the socket `/run/systemd/private` needed to retrieve the Systemd data, for example: ```bash docker run -d -v /var/run/docker.sock:/var/run/docker.sock:ro \ -v /proc/:/host/proc/:ro \ -v /sys/fs/cgroup/:/host/sys/fs/cgroup/:ro \ -v /run/systemd/:/host/run/systemd/:ro \ -e DD_API_KEY= \ datadog/agent:latest ``` #### Helm{% #helm %} For Helm configurations, you can set up the Datadog Agent to monitor systemd units (such as: `kubelet.service` and `ssh.service`) by defining volume mounts and volumes for accessing systemd-related files and directories within containers. For example: ```bash datadog: #(...) confd: # Custom config file for SystemD # Example: https://github.com/DataDog/datadog-agent/blob/main/cmd/agent/dist/conf.d/systemd.d/conf.yaml.example systemd.yaml: |- init_config: instances: - unit_names: - kubelet.service - ssh.service agents: # Custom Mounts for SystemD socket (/run/systemd/private) volumeMounts: - name: systemd mountPath: /host/run/systemd/ # the path within the container where the volume will be mounted volumes: - name: systemd hostPath: path: /run/systemd/ # the path on the host machine that will be mounted into the container. ``` {% /tab %} ### Validation{% #validation %} [Run the Agent's status subcommand](https://docs.datadoghq.com/agent/guide/agent-commands.md#agent-status-and-information) and look for `systemd` under the Checks section. ## Data Collected{% #data-collected %} ### Metrics{% #metrics %} | | | | | **systemd.service.cpu\_time\_consumed**(gauge) | The overall cpu consumed by the service in nanoseconds (CPUUsageNSec), requires Systemd configuration CPUAccounting to be enabled and Systemd version >= 220*Shown as nanosecond* | | **systemd.service.memory\_usage**(gauge) | The memory currently used by the service in bytes (MemoryCurrent), requires Systemd configuration MemoryAccounting to be enabled*Shown as byte* | | **systemd.service.restart\_count**(gauge) | The number of times the service has been restarted due to `Restart=` (NRestarts), requires Systemd version >= 235*Shown as time* | | **systemd.service.task\_count**(gauge) | The current number of tasks in the service (TasksCurrent), requires Systemd configuration TasksAccounting to be enabled*Shown as task* | | **systemd.socket.connection\_accepted\_count**(gauge) | The number of accepted socket connections (NAccepted)*Shown as connection* | | **systemd.socket.connection\_count**(gauge) | The current number of socket connections (NConnections)*Shown as connection* | | **systemd.socket.connection\_refused\_count**(gauge) | The total number of refused socket connections (NRefused), requires Systemd version >= 239*Shown as connection* | | **systemd.unit.active**(gauge) | Whether the unit is currently in active state | | **systemd.unit.loaded**(gauge) | Whether the unit is currently in loaded state | | **systemd.unit.monitored**(gauge) | Indicates that the unit is monitored (the value is always 1) | | **systemd.unit.uptime**(gauge) | The unit uptime in seconds since it's activation*Shown as second* | | **systemd.units\_by\_state**(gauge) | Sum by state to count units*Shown as unit* | | **systemd.units\_loaded\_count**(gauge) | The number of loaded units*Shown as unit* | | **systemd.units\_monitored\_count**(gauge) | The number of monitored units*Shown as unit* | | **systemd.units\_total**(gauge) | The total number of units*Shown as unit* | Some metrics are reported only if the respective configuration are enabled: - `systemd.service.cpu_time_consumed` requires Systemd configuration `CPUAccounting` to be enabled - `systemd.service.memory_usage` requires Systemd configuration `MemoryAccounting` to be enabled - `systemd.service.task_count` requires Systemd configuration `TasksAccounting` to be enabled Some metrics are only available from specific version of Systemd: - `systemd.service.cpu_time_consumed` requires Systemd v220 - `systemd.service.restart_count` requires Systemd v235 - `systemd.socket.connection_refused_count` requires Systemd v239 ### Events{% #events %} The Systemd check does not include any events. ### Service Checks{% #service-checks %} **systemd.can\_connect** Returns `OK` if Systemd is reachable, `CRITICAL` otherwise. *Statuses: ok, critical* **systemd.system.state** Returns `OK` if Systemd's system state is running. Returns `CRITICAL` if the state is degraded, maintenance, or stopping. Returns `UNKNOWN` if the state is initializing, starting, or other. *Statuses: ok, critical, unknown* **systemd.unit.state** Returns `OK` if the unit active state is active. Returns `CRITICAL` if the state is inactive, deactivating, or failed. Returns `UNKNOWN` if the state is activating or other. *Statuses: ok, critical, unknown* **systemd.unit.substate** Returns `OK` `CRITICAL` or `UNKNOWN` based on the substate of the unit and the user-provided mapping in systemd.d/conf.yaml. *Statuses: ok, critical, unknown* ## Troubleshooting{% #troubleshooting %} Need help? Contact [Datadog support](https://docs.datadoghq.com/help/).