Monitoring

LaserData Cloud provides built-in observability for every deployment. The Warden agent on each node collects metrics, heartbeats, and logs, and pushes them to the control plane where they're available in the Console and via API.

Metrics

Per-node, per-runtime metrics are collected continuously and available in the Console's metrics dashboard.

What's Collected

Category	Metrics
System	CPU usage, total CPU usage, memory usage, available memory
Process	Process ID, run time, start time
Disk I/O	Bytes read, bytes written
Iggy	Messages count, messages size, streams count, topics count, partitions count, segments count
Clients	Connected clients count, consumer groups count

Metrics are tagged by node and runtime (Iggy, Connectors), and can be filtered by time range.

Viewing Metrics

Navigate to your deployment in the Console
Open the Metrics tab
Select a node and runtime to view
Adjust the time range to zoom in on specific periods

Heartbeats

Warden sends periodic heartbeats for each managed runtime (Iggy, Connectors). Heartbeats indicate that the runtime is alive and responsive.

Heartbeats are viewable per node and per runtime
Time-range filtering for historical analysis
Missing heartbeats indicate a potential issue with the runtime

Logs

Centralized log collection from all runtimes on all nodes. Logs are ingested by Warden and stored for querying.

Searching Logs

Logs are searchable by:

Filter	Description
Node	Filter to a specific node
Runtime	Filter by runtime (Iggy, Connectors, Warden)
Level	Filter by log level (any, debug, info, warn, error)
Message	Pattern match on log message content
Scope	Filter by component
Time range	Start and end timestamps

Viewing Logs

Navigate to your deployment in the Console
Open the Logs tab
Apply filters to narrow down results
Logs are paginated for large result sets

Log Redirection (OpenTelemetry)

By default, all logs are collected and stored by the LaserData platform. If you prefer to keep log data in your own systems — for compliance, privacy, or integration with your existing observability stack — you can redirect logs to your own OpenTelemetry-compatible endpoint.

When log redirection is configured, the Warden agent on each node sends logs using the standard OpenTelemetry ExportLogsServiceRequest protocol. This means any OTEL-compatible collector, storage, or engine can receive your deployment logs — including Grafana Loki, Datadog, Elastic, or your own custom pipeline.

Traces are also supported via the OpenTelemetry ExportTracesServiceRequest protocol for deeper application-level observability.

To configure log redirection, contact support or manage it through the Console deployment settings.

Telemetry Retention

Telemetry data (metrics, heartbeats, logs) is retained based on your plan and can be configured per deployment:

Data Type	Configurable	Range
Metrics	Per deployment	7–365 days
Heartbeats	Per deployment	7–365 days
Logs	Per deployment	7–365 days

Default retention by plan:

Plan	Default Retention
Basic	7 days
Pro	90 days
Enterprise	365 days

You can adjust the retention period from the Console or API within your plan's limits.

Required permission: deployment:telemetry:read (view) or deployment:telemetry:manage (configure retention)

API Reference

Get Deployment Metrics

curl {supervisor_url}/deployments/{deployment_id}/metrics \
  -H "ld-api-key: YOUR_API_KEY"

Get Node Metrics (by runtime)

curl "{supervisor_url}/deployments/{deployment_id}/nodes/{node_id}/metrics/iggy?page=1&results=10&from=2026-01-01T00:00:00Z&to=2026-02-01T00:00:00Z" \
  -H "ld-api-key: YOUR_API_KEY"

Get Deployment Heartbeats

curl {supervisor_url}/deployments/{deployment_id}/heartbeats \
  -H "ld-api-key: YOUR_API_KEY"

Get Deployment Logs

curl "{supervisor_url}/deployments/{deployment_id}/logs/iggy?page=1&results=10&level=any&message=*&from=2026-01-01T00:00:00Z&to=2026-02-01T00:00:00Z" \
  -H "ld-api-key: YOUR_API_KEY"