Graylog

Graylog brings logs from different systems into one place for searching and investigation. It helps teams work with streams of operational records instead of signing into individual machines whenever an incident occurs. Configured processing and alerting can turn those records into useful signals for responders. Operating the service includes its log-storage backend, metadata and configuration, so the Kubernetes chart is only one part of a recoverable logging system.

Current guidance

This record originally linked to the community stable/graylog chart. Its final chart metadata declares deprecation and refers to Graylog 3.1; that archive is not a supported installation path for a current Graylog release. Graylog itself is a log management application with a separately published product and release policy.

The official compatibility matrix separates Graylog and MongoDB versions and distinguishes Data Node from self-managed OpenSearch deployments. Select one documented architecture before deciding which Kubernetes manifests or chart can implement it. Do not substitute a current search image into the archived chart and assume the data format, JVM settings and authentication remain compatible.

Plan persistence and recovery for the log store, MongoDB metadata and Graylog configuration. Size disk retention and ingestion buffering for the expected event rate, and protect administrative and ingestion endpoints independently. Rehearse a backup restore and a controlled dependency upgrade with representative queries and alerts. The container deployment guide helps identify persistent components, but it does not certify an arbitrary third-party Kubernetes chart.