Resource health in one view
Follow CPU utilization, memory, filesystem usage, load average and process count. Individual charts give a clearer picture than a single overall status.
Know your servers.
Before they need you.
Bring CPU, memory, disk, load and process metrics into the same workspace as your service checks. See the machine behind the response, with thresholds that suit the way it runs.
Part of your Uptiva workspace · One workspace. Every signal.
CPU34%
Memory61%
Disk48%
Load1.2
- Host
- production-web-01
- CPU
- 34%
- Memory
- 61%
- Disk usage
- 48%
An external check tells you a service is struggling. Host metrics give you another perspective: a full filesystem, sustained CPU pressure or a machine that has stopped sending data. Keep both views together to narrow down what deserves attention.
Connect a host with an OpenTelemetry Collector and review its resource charts, filesystems and network activity. Set thresholds and an evaluation window so sustained pressure receives attention without treating every short spike as an incident.
Keep this signal alongside the rest of your stack: organize related services, choose who receives alerts and follow recovery in the same workspace. The goal is a check that explains what changed and gives the right person a useful place to start.
SMALL DETAILS. USEFUL CONTEXT.More than
More than
an up or down.
Purpose-built checks.
Information you can act on.
Thresholds per host
Enable the checks you need and choose thresholds appropriate to the machine. A background worker and a database server do not need the same definition of healthy.
Look for sustained pressure
An evaluation window controls how long a metric must remain beyond its threshold. Use a shorter window for urgent systems or a longer one for workloads with normal bursts.
Notice missing data
The host is also watched for a stopped collector. A machine that goes silent can become down even when none of its resource thresholds was crossed in the last sample.
Filesystem and network detail
Review filesystems and network activity alongside resource trends. When disk usage surprises you, inspect the mounts rather than assuming the root filesystem tells the whole story.
Collector-based setup
Use the host page’s Linux installation instructions or its manual and Docker configuration. Each host has its own ingestion token, and the configuration belongs on that machine.
WHERE IT FITSMade for the work
Made for the work
you already do.
One reliable signal.
Plenty of practical uses.
Production application servers
Put resource pressure next to website and API availability. A slowdown is easier to investigate when you can compare it with CPU, memory and load in the same workspace.
Workers and background services
Watch long-running machines whose work is not represented by a public URL. Combine resource metrics with heartbeat monitoring for a fuller picture of scheduled jobs.
Growing infrastructure
Group hosts by purpose and compare their behavior as traffic grows. Keep threshold choices intentional instead of applying the same limits to every machine.
FROM SETUP TO A USEFUL SIGNALStart with what
Start with what
matters most.
Use a meaningful name, choose the behavior you expect and make sure the alert reaches someone who can act. Start with one service, then add the related checks as your monitoring grows.
Open the setup guide- 01
Choose your starting point.
Open Hosts, add a host and choose the resource checks and evaluation window that fit the machine.
- 02
Configure the check.
Use the installation command or collector configuration provided on the host page. Keep the host token private and allow outbound HTTPS to Uptiva.
- 03
Follow the signal.
Wait for the first metrics to arrive, then review the charts and tune thresholds using the normal behavior of that host.
A LITTLE MORE CONTEXTGood questions.
Good questions.
Clear answers.
The details that help you choose the right check and get a useful result.
Read the full documentationIs an agent required?+
Host monitoring receives metrics from the OpenTelemetry Collector contrib distribution. The host page provides installation and configuration instructions, including a Linux installer and a Docker setup.
Does a host use a monitor slot?+
Hosts have their own plan allowance and do not consume regular monitor slots. Availability and the number of hosts depend on the workspace plan; additional capacity may be available through add-ons.
What happens if the collector stops?+
A host that stops reporting is marked down after its evaluation window, with a minimum delay of about 90 seconds. This gives the collector time to send its next sample.
Does one CPU spike trigger an alert?+
A resource check requires the metric to stay beyond its threshold for the selected evaluation window. A single short spike does not meet that condition.
Can I rotate a host token?+
Yes. Rotate it from the host page and update the collector configuration promptly. The previous token stops working, so treat rotation as a configuration change for that machine.
LESS CHECKING. MORE KNOWING.One more thing
Get started One more thing
off your mind.
Bring host monitoring into your workspace.