Monitoring
Itential Gateway participates in the same monitoring and observability stack as Itential Platform: Prometheus for metrics, and Loki or the Elastic Stack for centralized logs. This page covers the facts specific to Gateway. For architecture, deployment steps, and full configuration reference, see Learn more.
Log file location
When Gateway runs as a server or runner, its log file is written to /var/log/gateway/gateway.log, owned by itential:itential with mode 0660. See Logging for CLI-mode log locations and format options.
If you’re deploying a log agent such as Alloy or Filebeat to collect this file, add the agent’s user to the itential group. Without that group membership, the agent fails to tail the file without raising an error you’d notice right away.
Loki job label
If you centralize logs with Loki and Alloy, label Gateway log streams job="iag". This is the label used throughout Itential’s Loki and Alloy label conventions and example LogQL queries.
Learn more
The rest of the monitoring stack, including architecture, deployment, and configuration, is documented in the Itential Platform monitoring guide:
- Monitoring overview — concepts and how metrics and logs fit together
- Exporters — Prometheus exporters, including how Gateway’s job queue depth signals fleet capacity
- Gateway metrics reference — every metric Gateway exposes
- Manage logs — choosing between Loki and the Elastic Stack
- Loki and Alloy deep dive — deployment, configuration, and LogQL examples