Configurations services - add a new field for service description

Hi @jstager, the name of the service is independent of how to monitor the service itself.

Why don’t you use directly the ifAlias in the name of the service?

Moreover, lot of plugin for service discovery doesn’t get other information than ifName.

Hi  Laurent,

There are different problems with adding the if-alias in the service name.

The descriptions of interfaces, the if-aliases, can have a certain length, adding this to the if-name in the same field for the service name makes visibility bad.

Especially since on one interface we have several checks for different alarms, different notifications, different graphics (traffic, errors, laser-dBm, sfp-environment) which must still be named differently, with a unique service name. Which makes readability even worse if everything is in the same field.

Also, the name of the service is used to generate the Centreon ID, if I'm not mistaken, it therefore does not have to be regularly modified. While the new description field, is there to be modified over time like the if-Alias change over time.

Not even mentioning that the service name is limited in illegal character

Here you can see an interface "HundredGigE0/0/0/0" which has 4 different checks/services. (Laser-dBm, Laser-env, Packet-Errors, Traffic) for readability, it is not desirable to also have the description of the interface in the same field.

This is why it would be very nice to have a “descrption” field.

Which is to be regularly modified, which can be displayed in the resource views and which can be find by search fileds.

There is already a “Additional Information/Comments" field, but it seems to be used nowhere...

Here you can see an example of description/if-alias that we have visible through Observium autodiscovery and which can also be found it in the search field dedicated to Aliases. We need the equivalent in Centreon

Here I exposed the case of if-name and if-alias for a network interface. But it certainly has many other application cases where a description field would be very useful for different Centreon users.

Thanks a lot

HI @jstager where do you want to use this new alias field? In monitoring table as column? Only in Service details panel?

Hi @Laurent 

yes, for me this is ideal and preferable if that it is visible as a new column of status resources. If necessary, this column could also be hidden/resize/moved by those who do not want to use it.

This should also be able to be found by the search fields

This should be able to be used in notifications commands.

Thanks a lot