Enhance: Translation of Service Descriptions
For Piggyback Data it is possible to translate service descriptions. Following features would enhance the functionality to normalize the description:
- Add Service Conditions
- Add an option to transform to upper / lower case only the "dynamic" part. For example when having Azure VM Check, Prefix VM should be transformed or not independently of the Name of the VM. This will help to have Hostname & Service Name Translation the same way, at least the Azure VM Status Check is used for host check Command with $HOSTNAME$ macro
General:
- Make it also working for non Piggyback Data as some software during update changes upper / lowercase or change version numbers, at least for Windows Services.
Possibly it can be merged with the "Alternative display name for Services" rule.
Comments: 5
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
05 Jan
Mohamed Saleh AdminHi Jan,
Thanks for posting on our Ideas Portal.
Just to make sure I don't confuse this with the rule set 'translation of service names', could you please paste a screenshot of the rule you refer to in this idea?
Best,
Saleh -
06 Jan
JanHi Saleh,
I talk about the "Translation of service description" rule.
We have an option for do case translations, multiple regular expression translations and explicit service description mapping.
To be honest, i hoped it will already work to mage case translation combined with multiple regular expressions, to match only some piggyback service descriptions.
For the "General" part in my initial idea, there is another rule "Alternative display name for Services" where i can define a name for a service by myself. But I cannot use a regex to make it kind of generic rule for different services and i also cannot convert it to upper / lower case.
Combine both rules in a new one and add a feature for case translation only for the dynamic part of a service name would be helpful. -
06 Jan
Mohamed Saleh AdminThanks Jan,
That helps to clarify.
For more context, could you explain your use case for changing case for only the dynamic part: what are the service names you want to convert the case and to what should the translation be? Also, what service conditions are most important to you? -
07 Jan
JanHi Saleh,
It might be a kind of individual problem, but maybe we are not the only ones. I have to split it in two comments. In Both cases it would be nice to be able to match the rule only to defined services, service labels etc.
1: Use Lower Case only for the dynamic part:
I attached a screenshot of the w32time service as example.
Sadly during Updates it sometimes happens in the windows world, that a service is reinstalled and changes its writing in terms of upper/lower letters. It would help to normalize the service name always to upper/lower but i don't think it makes sense to have the prefix "Service" also translated to lower case.
At least it would be nice to have it as a clickable option to translate only dynamic part or whole service description. -
07 Jan
Jan2: Use Lower Case of only for specific service names:
We do monitor Azure VMs by Piggyback Data. Not all the VMs are allowed to install the cmk agent and sometimes also not able to ping them.
As we use all lowercase servernames in CheckMK we want to use the VM Status Service (check_mk-azure_virtual_machine) as Host check command. Sadly the azure VMs do not follow the lower case, so we have mismatch of names using the $HOSTNAME$ macro in host check command rule. Other piggyback services of the same VM can keep their upper/lowercase letters as it might be easier to match the information with the original writing in other systems.
Translation_of_service_descriptions_bhe7ap.png
w32time_windows_service_y9vuyk.png