diff --git a/deployment/docker/alerts.yml b/deployment/docker/alerts.yml index 2ea932ba9..fd95441ff 100644 --- a/deployment/docker/alerts.yml +++ b/deployment/docker/alerts.yml @@ -125,7 +125,7 @@ groups: When VictoriaMetrics constantly hits the limit it means that storage is overloaded and requires more CPU." - alert: TooManyLogs - expr: sum(increase(vm_log_messages_total{level!="info"}[5m])) by (job, instance) > 0 + expr: sum(increase(vm_log_messages_total{level="error"}[5m])) by (job, instance) > 0 for: 15m labels: severity: warning diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index aa084dcd3..4266addda 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -15,6 +15,11 @@ The following tip changes can be tested by building VictoriaMetrics components f ## tip + +## [v1.78.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.78.0) + +Released at 20-06-2022 + **Update notes:** this release introduces backwards-incompatible changes to communication protocol between `vmselect` and `vmstorage` nodes in cluster version of VictoriaMetrics because of added [query tracing](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html#query-tracing), so `vmselect` and `vmstorage` nodes may log communication errors during the upgrade. These errors should stop after all the `vmselect` and `vmstorage` nodes are updated to new release. It is safe to downgrade to previous releases. * SECURITY: add `-flagsAuthKey` command-line flag for protecting `/flags` endpoint from unauthorized access. Though this endpoint already hides values for command-line flags with `key` and `password` substrings in their names, other sensitive information could be exposed there. See [This issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2753).