mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2026-05-17 00:26:36 +03:00
5632ccc64a
This simplifies troubleshooting by investigating the vm_log_messages_total metric when logs are unavailable. The logs may be unavailable when the -loggerLevel command-line flag is set to value other than INFO. The logs may be unavailable when clients use Monitoring of Monitoring service ( https://victoriametrics.com/products/mom/ ), which provides metrics, but doesn't provide logs from VictoriaMetrics components running at the client side. Add `is_printed` label to the `vm_log_messages_total` metric in order to detect whether the given log has been suppressed or printed. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10304 While at it, make more readable the description for the TooManyLogs alert, which is based on the vm_log_messages_total metric. Also return back the `level!="info"` instead of `level="error"` filter in the query for this alerting rule, in order to be consistent with queries at the official dashboards for VictoriaMetrics components. TODO: investigate too high warnings rate at https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2760 and fix it at the source of these warnings instead of modifying the query for the TooManyLogs alert.