Fully implement service tags instead of removing them
To our regret, the service tags have never been fully implemented and their full potential has never really been exploited.
One of the biggest advantages of tags is that they are predefined and therefore much less error-prone. For example, you can search/filter for services that do not have a certain tag or where the tag is not "empty" or "does not contain", and you can use the tags in views, which is not possible with labels. Therefore, we see the labels as a supplement to the tags, not as their replacement.
Host tags have proven their usefulness for a long time. That's why we would like to be able to use the service tags everywhere in the same way as the host tags. Basically, the only thing missing is the possibility of using the service tags and service auxiliary tags as a condition in rules.
https://forum.checkmk.com/t/deprecation-of-the-service-tags-feature/36073/1
Comments: 3
-
11 Jan, '23
HansFurther: labeling is as well not fully implemented.
Hence no replacement at all.
Deprecating an existing feature which is highly used is not customer friendly -
21 Jan, '23
MartinThe feature will not be deprecated. Focus however will be to improve the use of labels.
-
26 Jan, '23
Daniel@Hans
indeed also labeling is "incomplete" but in my opinion not as tags
But at least, we can hope we get this as well for the 2.2, which makes thinks easier as well
https://features.checkmk.com/suggestions/339982/support-regex-for-labels-in-rules