I have never understood why this is the case:
Create a service in XI in a config [file] called "Foo."
Name the service "Bar."
Duplicate the service because you want to add something similar.
Now there is a new service with a config [file] name of "Foo_copy_1" with a service called "Bar."
It would make much more sense to have a new service with a config [file] name that matches the original "Foo" and a service name called "Bar_copy_1."
Is there any way we can make this an option to do things this way in the future? Let people decide how they want to do it? It just seems weird that I select a config [file] from the pull down, duplicate my service, and now it's in an entirely different config [file].
Why does duplicate copy the config name, not service name?
Why does duplicate copy the config name, not service name?
Eric Loyd • http://everwatch.global • 844.240.EVER • @EricLoyd
I'm a Nagios Fanatic! • Join our public Nagios Discord Server!
Re: Why does duplicate copy the config name, not service nam
+1, I suggested this a while back.
According to Jake this has already been changed for 5.5.
According to Jake this has already been changed for 5.5.
Jake wrote: In 5.5 the service will be copied as Bar_copy_1 with the config name of Foo
Former Nagios employee
Re: Why does duplicate copy the config name, not service nam
Tell Jake I owe him something with bubbles.
Eric Loyd • http://everwatch.global • 844.240.EVER • @EricLoyd
I'm a Nagios Fanatic! • Join our public Nagios Discord Server!
Re: Why does duplicate copy the config name, not service nam
Will do. Locking this up.
Former Nagios employee