Can you provide an update and a rough timeframe of when these tasks will start to get worked?rkennedy wrote:The tracking system is internal only. I looked at 7193, and 7194 - at this point they are still in the developers to-do pool.
Feel free to post back when you'd like to check for an update once again.
Consolidated Services using Wizards
Re: Consolidated Services using Wizards
Re: Consolidated Services using Wizards
It looks like they are still waiting to be approved and assigned to someone. I can't provide a timeframe, as I do not have one available, the best I can provide is the current status.
Former Nagios Employee.
me.
me.
Re: Consolidated Services using Wizards
Can you provide an update on 7193 and 7194 in your tracking system?
Re: Consolidated Services using Wizards
They are still pending approval at this point.
Former Nagios Employee
Re: Consolidated Services using Wizards
Can you provide an update on 7193 and 7194 in your tracking system?
Re: Consolidated Services using Wizards
They have not yet been approved by the developer.
Former Nagios Employee.
me.
me.
Re: Consolidated Services using Wizards
While not as elegant as using the API, I'd probably create hostgroup, and host boilerplate files, search and replace strings such as hostgroup name, hostname, and address, drop the files into the import dir and run the reconfig script. This would add the host, the host to the hostgroup, and apply monitoring to services that have the hostgroup assigned to them.
The hostgroup base file needn't have all the hosts, just the one to add. Import doesn't remove, it only adds to or modifies what's already in the config.
Combine this with templates and you can separate monitoring from host and service definitions entirely.
The hostgroup base file needn't have all the hosts, just the one to add. Import doesn't remove, it only adds to or modifies what's already in the config.
Combine this with templates and you can separate monitoring from host and service definitions entirely.
Re: Consolidated Services using Wizards
Thank you for the suggestion. That may be the route taken, depending on how long it takes for the API to be approved and rolled out. My co-worker who is working on that section wants to use the API and avoid file manipulation.gormank wrote:While not as elegant as using the API, I'd probably create hostgroup, and host boilerplate files, search and replace strings such as hostgroup name, hostname, and address, drop the files into the import dir and run the reconfig script. This would add the host, the host to the hostgroup, and apply monitoring to services that have the hostgroup assigned to them.
The hostgroup base file needn't have all the hosts, just the one to add. Import doesn't remove, it only adds to or modifies what's already in the config.
Combine this with templates and you can separate monitoring from host and service definitions entirely.
Re: Consolidated Services using Wizards
Thanks for the help, @gormank.
@chicjo01, I apologize this has not been implemented yet, the developers have a very high load at all times, and not all feature requests make it within a month or two of them being requested.
@chicjo01, I apologize this has not been implemented yet, the developers have a very high load at all times, and not all feature requests make it within a month or two of them being requested.
Former Nagios Employee.
me.
me.
Re: Consolidated Services using Wizards
Hi,
Can you provide an update on 7193 and 7194 in your tracking system?
Thanks
Can you provide an update on 7193 and 7194 in your tracking system?
Thanks