Doing some rearchitecting/reorganization of our services and wonder how people were using config name.
In our place, it's often just a synonym for host.
How are you guys using config name?
Best Practice Convention for Config Name
Re: Best Practice Convention for Config Name
If it is a service that is only on that one host, that is definitely the best practice. If it is a generic service definition that gets assigned to multiple hosts then really, whatever makes the most sense to you.
If it is only for that one host and it isn't the exact same as the host name then you can't use the configure tab on the service detail page.
If it is only for that one host and it isn't the exact same as the host name then you can't use the configure tab on the service detail page.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
Re: Best Practice Convention for Config Name
Thanks, BanditBBS!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Best Practice Convention for Config Name
Oh, that's a perfect way to look at it, thanks!
-
jdalrymple
- Skynet Drone
- Posts: 2620
- Joined: Wed Feb 11, 2015 1:56 pm
Re: Best Practice Convention for Config Name
Is your question answered so we can lock the topic and mark solved?
Re: Best Practice Convention for Config Name
Yes, it is, thanks.