Skip to content

Commit 85a0f1a

Browse files
crazyscientistTimotheusBachinger
authored andcommitted
Update werk 19801
CMK-33299 CMK-33213 Change-Id: I9c985a4e5350eda9230451d515f4594dfeb42357 (cherry picked from commit 611433d)
1 parent ca7363d commit 85a0f1a

2 files changed

Lines changed: 7 additions & 26 deletions

File tree

.werks/19800.md

Lines changed: 0 additions & 20 deletions
This file was deleted.

.werks/19801.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,12 @@ component | checks
1111
level | 2
1212
compatible | no
1313

14-
If the services on a host are short-lived and plentiful, e.g. like the containers and volumes in a K8S cluster, services
15-
may never appear again.
16-
During service discovery, they would simply show up as disabled with the summary "Item not found in monitoring data".
17-
Unlike services shown as "vanished", they are never removed.
14+
Previously, services configured to be ignored by the "Disabled services" ruleset were written into the autochecks file.
15+
Moreover, they were never removed from autochecks, even when they vanished from the data source content.
1816

19-
With this werk, these services are consistently displayed as vanished instead.
20-
This allows for the services to be removed during discovery; manually or automatically.
17+
This led to ever-growing autochecks files — especially on hosts with volatile services, such as those in Kubernetes or Docker environments, but not limited to these.
2118

19+
With this Werk, services matched by "Disabled services" are no longer written into autochecks.
20+
Previously accumulated entries for such services will now appear as vanished during service discovery.
21+
22+
To clean up existing autochecks, run a re-discovery on the affected hosts to remove these services.

0 commit comments

Comments
 (0)