Hetzner Cloud Integration
Monitor server metrics, load balancer health, and network traffic across your Hetzner Cloud infrastructure. Track bandwidth quotas, detect unexpected server terminations, and correlate VM health with application performance.
How It Works
Deploy hetzner-exporter via Helm
Add the TigerOps Helm chart to your Kubernetes cluster or Docker Compose stack. Provide your Hetzner Cloud API token and the exporter auto-discovers all servers, load balancers, volumes, and floating IPs in your project.
Configure Remote Write
Point the exporter to your TigerOps remote-write endpoint. Server CPU, memory, disk I/O, and network metrics begin flowing in within minutes. Load balancer request rates and health check statuses are collected via the Hetzner Cloud API.
Set Resource Thresholds
Define per-server CPU, disk, and network thresholds. TigerOps alerts when servers approach resource limits and detects when servers are stopped or terminated unexpectedly — catching runaway costs and outages in real time.
Correlate Infrastructure with Application
TigerOps links Hetzner server metrics with your application-level traces and logs — correlating VM CPU spikes with increased latency in services running on those servers for complete incident context.
What You Get Out of the Box
Server CPU & Memory Monitoring
Per-server CPU utilization, memory usage, and load averages collected from the Hetzner Cloud Metrics API. Track trends and alert when servers are consistently over-provisioned or approaching saturation.
Load Balancer Health Tracking
Monitor Hetzner Load Balancer request rates, connection counts, open connections, and backend health check statuses. Alert when backends fail health checks or when a load balancer approaches its connection limit.
Network Traffic Monitoring
Track inbound and outbound network traffic per server and per load balancer. Monitor bandwidth utilization against your Hetzner plan's included traffic allowance and alert before overage charges accrue.
Disk I/O & Volume Health
Monitor Hetzner server disk read/write throughput and IOPS. Track attached volume utilization and alert when disk I/O saturation is causing application performance degradation.
Server Lifecycle Events
Track server start, stop, rebuild, and rescue events from the Hetzner Cloud API action log. Correlate unexpected server terminations with application downtime events for full incident reconstructions.
AI Root Cause Analysis
When application latency spikes on Hetzner infrastructure, TigerOps AI correlates server CPU and disk I/O metrics, network saturation, load balancer backend health, and recent infrastructure changes to identify the cause.
Helm Values for hetzner-exporter
Deploy the TigerOps Hetzner Cloud exporter to your Kubernetes cluster with these Helm values.
# TigerOps hetzner-exporter Helm values
# helm repo add tigerops https://charts.atatus.net
# helm install hetzner-exporter tigerops/hetzner-exporter -f values.yaml
hetznerExporter:
# Hetzner Cloud API token (read-only)
apiTokenSecret:
name: hetzner-credentials
key: api_token
# Resource types to monitor
resources:
servers: true
loadBalancers: true
volumes: true
floatingIPs: true
networks: true
# Label filters (monitor servers with these labels)
serverLabelSelector:
environment: production
# Metrics collection interval
scrapeInterval: 60s # Hetzner Metrics API max resolution is 1 minute
remoteWrite:
endpoint: https://ingest.atatus.net/api/v1/write
bearerToken: "${TIGEROPS_API_KEY}"
scrapeInterval: 60s
# Alert thresholds
alerts:
serverCpuWarningPct: 80
serverCpuCriticalPct: 95
networkBandwidthWarningGbps: 1.0
monthlyTrafficWarningPct: 80 # % of included plan traffic
loadBalancerUnhealthyTargets: 1Common Questions
How does TigerOps collect metrics from Hetzner Cloud?
TigerOps uses two Hetzner APIs: the Hetzner Cloud Metrics API for server time-series data (CPU, disk, network) and the Hetzner Cloud REST API for resource inventory and action events. A read-only API token with resource scoping is sufficient.
What Hetzner Cloud API token permissions does TigerOps need?
TigerOps requires a read-only Hetzner Cloud API token. In the Hetzner Cloud Console, create a token with Read permission only. TigerOps never writes to your Hetzner infrastructure — it only reads metrics and events.
Can TigerOps monitor multiple Hetzner Cloud projects?
Yes. Add one API token per Hetzner Cloud project. Resources are labeled with the project name so you can view cross-project infrastructure health in unified dashboards and set project-scoped alert routing.
Does TigerOps support Hetzner Cloud Placement Groups and Private Networks?
Yes. Server metadata including placement group membership and private network assignments are collected as labels. You can filter dashboards and alerts by placement group or network, making it easy to monitor specific server clusters independently.
Can TigerOps alert when my Hetzner traffic quota is approaching the monthly limit?
Yes. TigerOps tracks cumulative monthly traffic per server against your Hetzner plan's included traffic allowance. You can set alerts at configurable percentages (e.g., 70% and 90% of monthly allowance) to avoid surprise overage charges.
Stop Discovering Hetzner Bandwidth Overages After the Bill Arrives
Server health alerts, load balancer monitoring, and traffic quota tracking. Deploy in 5 minutes.