Closed (fixed)
Project:
Nagios Monitoring
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 May 2010 at 13:09 UTC
Updated:
2 Jan 2014 at 19:06 UTC
Jump to comment: Most recent
Comments
Comment #1
kjv1611 commentedI'm not involved in this project in any way, but could you please expand on your thoughts that it's a pretty critical piece of the infrastructure? I mean its integrating something totally outside Drupal, so how could that in any way be critical?
Comment #2
kbahey commented@Damien
You are right. I would love to create a stable release.
What do you think of this. Should we wait for a resolution, or just roll out a stable?
#672264: No default "Unique ID" or make it unique
Less important ..
#794074: Run checks for a specific module or a specific check inside a module
#764576: check_drupal contains extranious shift while processing -S option
Comment #3
greg.harveyWhat's the news on this... it's been a while folks. We're just starting to use this and it seems good. There are a few niggles, but I see no reason not to have a 6.x-1.0?
Comment #4
greg.harveyWill try and do this soon as. #764576: check_drupal contains extranious shift while processing -S option is so tiny I'll include it (quickly checked utils.sh and that makes sense).
Also want to include #989932: Enable NRPE checks with exposure to Drush in the first proper release, but we're using it already so I'm confident it will be stable and safe and not do any bad things to anyone else.
I'm inclined to ignore #672264: No default "Unique ID" or make it unique for now, though I have read it and we can certainly create a new issue for the requirements check ASAP.
So unless someone comes back with violent objects, I propose to roll a 6.x-1.0-beta1 release next week with these patches committed:
- #764576: check_drupal contains extranious shift while processing -S option
- #989932: Enable NRPE checks with exposure to Drush
Then I'll create a 6.x-1.0 release when these patches are ready:
- #1110654: Implement a hook_requirements() function to make sure a unique ID is set
- #1091314: Requirements warning in Drupal creates a Critical warning in Nagios
- (if some consensus is reached) #672264: No default "Unique ID" or make it unique
Then we can start thinking about #1091318: Port Nagios monitoring to Drupal 7. =)
Comment #5
greg.harveyOk, my criteria for a beta official release are now met. I will do this later...
Comment #6
greg.harvey6.x-1.0-beta1 released! The first *ever* Nagios release. =)
So, now to push on to the 6.x-1.0 release before contemplating a D7 port.
Comment #7
anavarreSubscribe
Comment #8
greg.harveyOnly one issue left stopping 6.x-1.0. I'll see if I can make time this week. Adding to TODO.
Comment #9
greg.harveyOK, finally done everything. 6.x-1.0 is out.
I know this is back to front, but right now I (as the only active maintainer) only have Nagios running on Drupal 6 sites, though that will change very shortly indeed. Next stop, Drupal 7 point release. I'll start a new thread for that.