Skip to main content

Features

What you get out of the box when you run the AtherOps Linux Agent.

Host metrics​

Continuous collection of CPU, memory, disk, network, filesystem, and load-average metrics from every host. Sampled every 15 seconds by default, configurable per host. No additional setup — these are on as soon as the agent starts.

Process metrics​

Per-process CPU, memory, and I/O metrics for the top-N processes by memory usage on each host. Surfaces noisy neighbors and runaway workloads without exporting metrics for every PID. Top-N count is configurable.

Container metrics​

Per-container CPU, memory, and I/O metrics, collected from the local Docker socket. Automatically enabled when Docker is present and silently skipped when it isn't, so the same agent works on hosts with or without containers.

Log collection​

Tail any log file on the host and forward lines to the AtherOps platform. The agent also reads systemd journal output, so you get journalctl-style logs without any additional setup. Each log source can carry custom labels for filtering and grouping in the UI.

Distributed tracing​

Optional OTLP receiver lets your applications send distributed traces directly to the agent. Point your OpenTelemetry SDK at the agent's :4317 (gRPC) or :4318 (HTTP) endpoint and traces flow to AtherOps alongside metrics and logs.

Application metrics​

Scrape any Prometheus-style /metrics endpoint exposed by your own services. The agent collects them on the same schedule as host metrics and forwards them through the same secure channel — no need for a separate Prometheus server on the host.

Automatic registration​

Provide a one-time install token at install time and the agent registers itself with the platform on first boot. No manual API-key copy-paste, no per-host configuration files to ship around.

Automatic key rotation​

The agent rotates its credentials on a configurable cadence (30 days by default). If the platform ever revokes a key, the agent automatically re-registers without intervention.

Remote configuration​

Configuration updates can be pushed from the platform — change scrape intervals, log targets, or feature toggles fleet-wide without re-running the installer or restarting hosts manually.

Lightweight footprint​

Single agent, single config file. The agent only makes outbound connections — it never accepts traffic from the public internet. All data is authenticated in transit.