Grafana Alloy

Managed monitoring built around Grafana Alloy collectors.

Nova installs Grafana Alloy on Linux hosts, manages collector enrollment, and routes host telemetry into managed metrics, logs, dashboards, and alerts.

Install path
Generated one-time collector install command
Config
Remote configuration pulled from NovaCFG
Telemetry
Linux metrics, journal logs, selected file logs, optional Docker
Visualization
Grafana dashboards opened through Nova SSO

Why Nova uses Grafana Alloy

Grafana Alloy is the collector that runs on each monitored Linux host. Nova uses Alloy because it can collect host metrics and logs, run as a service, and be configured centrally for a focused managed monitoring workflow.

In Nova V1, customers do not need to design Alloy pipelines from scratch. The product creates a collector, provides an install command, and manages the expected remote configuration for the supported telemetry scope.

Collector enrollment flow

A Nova admin creates a collector in the control plane and receives a generated installer. The installer sets up Grafana Alloy, writes the remote config URL, starts the Alloy service, and lets Nova track whether the collector is online, warning, offline, or never connected.

This creates a controlled enrollment path with one-time tokens, tenant limits, and usage tracking instead of unmanaged agents sending telemetry without a tenant context.

What remains managed by Nova

Nova owns the tenant model, role mapping, collector status, remote config, gateway routing, Grafana organization mapping, and core dashboards. That lets the customer focus on monitored hosts instead of maintaining the observability platform.

  • Alloy health and host status checks.
  • Remote configuration for supported Linux monitoring features.
  • Metrics and log routing to managed backends.
  • Grafana access through Nova OIDC claims.