Skip to content
Telemetry
For teams tracking containers, hosts, processes, disks, and network metrics

Infrastructure metrics with SQL

Send structured infrastructure events when you need queryable host and container history without a large monitoring rollout.

Reviewed by the Telemetry product team on . We checked the event fields, suggested queries, and data to exclude. Who reviews this page

Why this works
  • Analyze container, disk, process, system, and network metrics with SQL.
  • Join operational metrics to product or customer events when needed.
  • Start with a few metrics and set alert thresholds after checking their normal ranges.
How to test this use case

Measure Infrastructure metrics with SQL and check the results

To measure infrastructure metrics with sql, choose one workflow and its owner. Define the events, test them with known inputs, and write a query that answers a specific question.

  1. 1

    Choose when to log

    Log metric snapshots with host, container, process, and environment labels.

  2. 2

    Capture the outcome

    Begin with container_metric_recorded, disk_metric_recorded, system_metric_recorded and document the grain of each event.

  3. 3

    Check the stored rows

    Alert on threshold breaches, trend changes, and missing heartbeats.

  4. 4

    Make the decision

    Which containers or hosts are under sustained pressure?

Agent prompt

Paste this into your coding agent

Replace YOUR_API_KEY after signup, then ask the agent to run the product flow and verify the first events.

agent prompt

Infrastructure metrics with SQL setup prompt

text
Instrument infrastructure metrics with Telemetry.

Use /skill.md and this Telemetry API key: YOUR_API_KEY

Please log container, disk, system, network, process, and heartbeat metrics. Include host_name, container_name, environment, metric_name, metric_value, unit, threshold, status, and observed_at.

Create dashboards for CPU, memory, disk, network, process health, and missing heartbeats. Add alerts for sustained threshold breaches and missing data.

Do not log secrets, environment variable values, command arguments containing credentials, or raw process payloads.

Setup steps

  1. 1Log metric snapshots with host, container, process, and environment labels.
  2. 2Keep metric names stable and put high-cardinality identifiers in fields.
  3. 3Create dashboards for CPU, memory, disk, network, and process health.
  4. 4Alert on threshold breaches, trend changes, and missing heartbeats.

Events to capture

container_metric_recordeddisk_metric_recordedsystem_metric_recordednetwork_metric_recordedprocess_metric_recordedheartbeat_missing

Questions you can answer

  • Which containers or hosts are under sustained pressure?
  • Which processes correlate with product incidents?
  • Which hosts have stopped reporting heartbeats or are running out of disk space?

Example event schemas

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

Use these queries in Telemetry

Learn about Alerts

Add a threshold and recipients to your reliability query to get alerts.

Related SQL recipes

More SQL recipes

Run the query using this workflow's event fields and check the example result. Save the result to a dashboard or set up an alert.

Browse all recipes

Next step

Create the API key your agent will use

The free plan is enough to run the prompt, send test events, and review the first dashboard.

Related pages