VictoriaMetrics

mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2026-05-17 00:26:36 +03:00

Files

Aliaksandr Valialkin 5632ccc64a lib/logger: count both printed and suppressed logs at vm_log_messages_total metric

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.

2026-01-25 17:43:20 +01:00

flag.go

lib/logger: prettify logging the defined command-line flags

2022-08-07 22:58:29 +03:00

json_fields.go

lib/logger: follow-up for 72f8fce107

2022-12-16 17:42:07 -08:00

logger_test.go

all: consistently use 'any' instead of 'interface{}'

2024-07-10 00:20:37 +02:00

logger.go

lib/logger: count both printed and suppressed logs at vm_log_messages_total metric