Troubleshooting logging

Logs are not displayed, Vector does not collect.

If logs do not appear on the Logs tab of the cluster dashboard, check collection and storage using the scenarios below.

Logs are not displayed #

• Ensure the local log collection module (shturval-log-collector, Vector) is enabled in the cluster.
• Verify that shturval-metrics-collector (monitoring module management / log storage component) is running in the management cluster.
• Check the VictoriaLogs instance for the cluster (VLSingle custom resource in the cluster namespace in the management cluster).
• Verify pod status (Running, Ready) and namespaces: shturval-log-collector in the cluster namespace; shturval-metrics-collector and VictoriaLogs in the management cluster.

Logs are not received #

• Check shturval-log-collector and VictoriaLogs pods (cluster namespace and management cluster).
• Review Vector logs (shturval-log-collector).
• Ensure cluster pods write logs to stdout/stderr.
• Verify network connectivity between Vector and VictoriaLogs.

Storage full #

• Set up log rotation in VictoriaLogs (retentionPeriod);
• Reduce retention or the volume of logs collected.

See also #

• Platform administrator logs - architecture, Vector pipelines, integration with external storages
• How to redirect logs - setting up sinks and platform_logs_sink