Skip to main content
Declined

Automatic cleanup of service name during autodiscover

Related products:Infra Monitoring - Discovery
  • February 27, 2025
  • 3 replies
  • 27 views

Forum|alt.badge.img+17

hello

based on that post : Characters allowed in servce name | Community

and an issue I encountered lately, with autodiscover getting invalid characters in the service name (for which I need help invalid characters in service autodiscover | Community)

 

 

could there be an update in autodiscover engine something that check and replace all the “invalid” character, like a "-” before pushing (and breaking) the poller config?

 

the option  to remove the char, replacing them with nothing could provoke some overlap, there are less chance by replacing with another valid char, “-” (dash) is more safe to use but that’s just my opinion.

 

the alternative of changing the plugin is not a valid solution (because the service name is usually based on the instance you need to monitor with its invalid character, if it is filtered at plugin level, how to know which instance to filter), plus it would require re-developping all plugin that could return invalid character 

 

that issue may just be isolated to that plugin I’m using (fortinet / Traffic autodiscover), but I wouldn’t be surprised if there were other cases for other technologies, especially with more and more cloud things or exotic systems.

 

thanks for reading

3 replies

rchauvel
Centreonian
Forum|alt.badge.img+18
  • Centreonian
  • March 7, 2025

Declined as this is more of a bug than an idea. We are going to put this as a bug in the product backlog.


rchauvel
Centreonian
Forum|alt.badge.img+18
  • Centreonian
  • March 7, 2025
NewDeclined

Forum|alt.badge.img+17
  • Author
  • Centreon Lord Commander
  • March 7, 2025

hello

yes, I have only encountered that on the fortinet plugin