Skip to main content

Grafana Alloy (alloy)

Collects the journal of the navin-* units and the files under /var/log/navin and ships them as OTLP logs to the OpenTelemetry Collector (then OpenSearch); optional metrics remote write.

Generated from catalog/services/alloy.yaml: do not edit by hand.

Summary​

Version1.10.0
Useinstall and configure
Layerinfrastructure (shown apart)
CategoryObservability
Installation methodsbinary
External connectionno
Sandbox onlyno

Licence​

SPDX identifierApache-2.0
Licence policycore licence (MIT or Apache-2.0)
Licence exception-
Platform componentalloy

Packages and artifacts​

A package the project of the service publishes (its image, its binary archive, its Python or OS package) carries the licence of the service; a third-party package carries the licence written on its row, read from the official upstream metadata.

KindPackageVersionLicenceDetails
binary archivealloy-linux-amd64.zip1.10.0Apache-2.0https://github.com/grafana/alloy/releases/download/v1.10.0/alloy-linux-amd64.zip, x86_64, checksum sha256

Supported systems and architectures​

MethodOperating systemsArchitectures
binaryRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64 (architecture of the artifacts of the descriptor)

Certified host systems: RHEL 8/9/10, Rocky Linux 8/9/10, AlmaLinux 8/9/10, Oracle Linux 8/9, CentOS Stream 9/10, Ubuntu 22.04/24.04, Debian 12, Arch Linux (rolling). The host preflight accepts these systems (other releases of a known family give a warning, end of life releases are refused) and the x86_64 and aarch64 architectures.

Prerequisites​

Host​

The descriptor declares no host preflight check.

Network and ports​

ComponentPort namePortOpened in the host firewall
alloyhttp12345/tcpno

Services and connections needed​

Details and resolution: see Dependencies.

Installation methods and modes​

MethodDefaultWhat the method uses
binaryyesthe binary archives of the descriptor, unpacked under the service directory

Components​

ComponentKindInstallation methodsPorts
Alloy agent (alloy)workerbinary12345/tcp

Every host (every-host) (default)​

One agent per managed host.

What the mode deploys:

ComponentPlacement
alloymin 0, recommended 3

Install this service​

The install wizard of the Navin Manager plans, validates and runs the installation; you need the services:install permission on the cluster.

  1. Open the wizard. In Clusters, choose the row action Install services of the target cluster. The wizard opens on its first step, Service.

  2. Choose the service. On the Service step, select Grafana Alloy. The card shows the licence Apache-2.0 and the dependencies the installation needs.

  3. Choose the hosts and the mode. On the Hosts step, tick the hosts, then choose the Mode: every-host (default). Each mode deploys the components listed in Installation methods and modes.

  4. Bind the dependencies. On the Bindings step, choose for each dependency (otel, prometheus, tetragon) Install with the platform or Use an existing connection; an optional dependency can stay on No binding.

  5. Configure. On the Configure step, review the parameters (see Configuration parameters). Passwords left empty with a generated default are generated and sealed by the Manager.

  6. Review and install. On the Install step the Manager validates the plan and shows the installation order; when it says "The plan is valid. Ready to install.", choose Install. A highly available mode is installed only when its HA checks pass.

  7. Verify. The operation ends when the health checks of every instance pass (see Health checks); the service then shows as running in Services.

High availability​

Clusterper host (per-host)
High availabilityper host (per-host)
Failovernone (none)
Replicationnone (none)
Quorumnone (none)
Discoverystatic (static)
Entry pointper host (per-host)
Official documentationhttps://github.com/grafana/alloy/blob/main/docs/sources/configure/clustering/configure-alloy.md

Prerequisites​

PrerequisiteMust be highly availableModesDescription
otelnomodes of level ha or clusterOpenTelemetry Collector receiving the data of the agents; replicate it (gateway mode) so that an agent always has a destination.

Topology per mode​

ModesHighest catalog levelDistributionQuorum componentFault domainsDescription
every-hostha (ha)per host (per-host)--One agent on every host: each host covers itself, the loss of a host only loses its own coverage.

Notes​

  • Alloy clustering is enabled component by component (only the compatible components share their work); the catalog mode runs one independent agent per host and does not enable it.

Configuration parameters​

General​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
HTTP port (port)port12345-nononoPort of the Alloy interface and metrics, bound to the host address.
TLS (tls_enabled)boolfalse-nononoServe the interface and the metrics over HTTPS (http block, tls) with a certificate issued by the manager CA; Prometheus then scrapes it in https and verifies it with that CA.
Log directory (log_root)path/var/log/navin-nononoDirectory whose *.log files are shipped.
Send host metrics (remote_write_metrics)boolfalse-nononoRemote write the Unix exporter metrics to the Prometheus binding.

Dependencies​

For each active dependency the Manager takes the first of: the binding chosen in the wizard; a service of the same installation that provides it; a service already installed in the cluster; the only connection of the expected type. Otherwise an optional dependency stays unbound, and a required one is added to the installation in its default mode (the column below names the catalog service added).

BindingProvided byConnection typeEndpointOptionalWhen nothing is boundDescription
otelotel-collector-otlp_httpnootel-collector is added to the installationOpenTelemetry Collector receiving the logs (OTLP over HTTP).
prometheusprometheus-httpyesstays unbound (optional)Prometheus receiving the host metrics by remote write.
tetragontetragon-metricsyesstays unbound (optional)Tetragon whose metrics stay on the loopback of its hosts (metrics_local): Alloy scrapes them on its own host and sends them to Prometheus by remote write.

Endpoints​

EndpointSchemeComponentPortPathTLS parameterBinding parametersBinding secretsProvisioning command
httphttpalloy12345 (port)-tls_enabled---

Health checks​

Liveness (per instance)​

ComponentCheckDetails
alloyHTTP {{ 'https' if config.tls_enabled else 'http' }}://{{ host.fqdn if config.tls_enabled else (host.ip or '127.0.0.1') }}:{{ config.port }}/-/readyExpected 200; 30 retries; interval 1 s; timeout 3 s

Uninstall​

Paths removed when the data is purged: {{ paths.data }}.

  • Alloy interface: {{ 'https' if config.tls_enabled else 'http' }}://{{ host.fqdn }}:{{ config.port }}/

Upstream documentation​