HYPHAby S33D
Documentation › Integrations

System, web and mail integrations

The agent recognises installed software and collects its metrics, with Datadog-compatible names. Most integrations turn themselves on.

How it works

Settings go under integrations.<name> in the configuration. Databases have their own page: Databases.

Web servers and load balancers

IntegrationSourceMain metricsActivation
nginxstub_status pagenginx.requests, nginx.connections.active, .reading, .writing, .waitingenabled: true and url
apachemod_status (?auto)apache.net.hits, .request_per_s, .bytes_per_s, apache.performance.busy_workers, .idle_workers, apache.conns_totalauto
haproxyadmin socket (show stat) or CSV pagehaproxy.frontend.*, haproxy.backend.*, haproxy.server.*, haproxy.backend_up, haproxy.server.upauto
iis (Windows)performance countersiis.requests_per_s, iis.current_connectionsauto

For nginx, open the status page to the loopback only:

location /nginx_status { stub_status; allow 127.0.0.1; deny all; }
integrations:
  nginx: {enabled: true, url: http://127.0.0.1/nginx_status}
  apache: {enabled: auto, url: "http://127.0.0.1/server-status?auto"}
  haproxy: {enabled: auto, socket: /run/haproxy/admin.sock}   # or url: http://127.0.0.1:8404/stats;csv

nginx, Apache and HAProxy access logs are parsed on arrival: method, path, HTTP code, duration, client address. See Logs.

PHP-FPM, Varnish, Squid, Lighttpd, Gunicorn and Supervisor, as well as PowerDNS, OpenLDAP, Keycloak, Nexus, Harbor, ZooKeeper and Ceph, have their dedicated probes: see Applications and services.

Jenkins, GitHub (and GitHub Enterprise Cloud), the Zot registry and Odoo: see CI, forges and business apps.

DNS

bind reads the JSON statistics channel (statistics-channels { inet 127.0.0.1 port 8053; };), otherwise rndc status. Metrics: bind.queries by type, bind.responses.nxdomain, bind.responses.servfail, bind.zone.serial per zone, bind.recursive_clients.

Pi-hole, AdGuard Home and Unbound, as well as Caddy, MinIO, Mosquitto, Proxmox Backup Server, Borg and restic, have their own page: Network, storage and backups.

Mail

IntegrationSourceMetrics and checks
postfixpostqueue -j and delivery logspostfix.queue.size per queue (active, deferred, hold, incoming), postfix.delivery.sent, .deferred, .bounced
dovecotdoveadm stats dump, doveadm whodovecot.auth.success, .failures, dovecot.connections
rspamdlocal /stat pagerspamd.messages.scanned, .learned, .spam, .ham, rspamd.actions per action, rspamd.connections
exchange (Windows)performance countersexchange.queue.<state> per transport depot, exchange.database.mounted (and check), exchange.imap.connections; checks for poison and suspended messages

To check mail end to end (SMTP banner, IMAP, send then fetch, SPF, DKIM, DMARC, blocklists), see mail synthetic tests.

Security and access

integrations:
  ssh:
    targets:
      - {name: bastion, address: "bastion.example:22", expect_banner: "^SSH-2.0-OpenSSH_9"}
      - {address: 192.0.2.10}          # port 22 by default

Certificates

x509 watches the certificates installed on the host: tls.cert.days_left and the tls.cert.expiry check (warning under 21 days, critical under 7 days), read every hour.

The Certificates page of the interface gathers every certificate collected by agents and synthetic tests, sorted by expiry.

Hardware and system

IntegrationSourceMetrics and checks
smartsmartctl, every 30 min, without waking a sleeping disksmart.health, .temperature, .reallocated_sectors, .power_on_hours, .wear_level
hwmon/sys/class/hwmonsystem.temperature, system.fan.rpm
ntpchronyc, timedatectl or ntpq; w32tm on Windowsntp.offset, ntp.in_sync check
updatespackage manager cache (no apt update), read every hoursystem.updates.pending, .security, system.reboot_required; Windows: windows.updates.pending check
systemd_timerssystemctlsystemd.timer check: critical if the last run failed, warning if an active timer has not run for two periods
virtualboxaccounts' VirtualBox.xml and processesvirtualbox.vms.running, .total, virtualbox.vm.running check for autostart VMs
btrfs/sys/fs/btrfs (error counters: kernel 5.14 and later, otherwise btrfs device stats)per mounted filesystem: btrfs.allocated, .used, .usage per type (usage_type) and profile (replication_type), btrfs.unallocated and .unallocated.pct, btrfs.device.errors; btrfs.health check: critical if a device is missing, warning if error counters are not zero
nfsclient: /proc/1/mountstats; server: /proc/net/rpc/nfsdclient, per mount: operations, bytes read and written, average round-trip and execution times, retransmissions, timeouts, usage; nfs.mount check (critical if statfs does not answer within timeout, 5 s: hung mount). Server: nfsd threads, RPC calls and bad calls, bytes, operations per version, exports; nfs.server check

An NFS server in a container keeps its statistics in its own network namespace: integrations.nfs.server_stats: /proc/<container pid>/net/rpc/nfsd. nfs.mounts restricts the followed mounts (patterns).

Processes, ports and pages

Without any specific integration, the agent can also check:

Your own metrics

The agent listens for StatsD in DogStatsD format on 127.0.0.1:8125/udp, aggregates over 15 seconds and sends everything as regular metrics:

echo "shop.orders:1|c|#env:prod" | nc -u -w0 127.0.0.1 8125

For an application that already publishes Prometheus metrics, Nagios or Centreon plugins, or logs sent over syslog, see Generic collection.

Counters (c) become sums, gauges (g) values, timers (ms, h) distributions (.avg, .max, .p50, .p95, .p99, .count). For OpenTelemetry metrics, see Traces.

Updated: 20 November 2026