#1 Possible conflict matching service names
e-mail address=roberto.oliver@frape.behrgroup.com
tested with 2 versions:
NagiosGrapher-1.6.1-rc3a, and
NagiosGrapher-1.6.1-rc5-0.5
When using similar service names ('3DEvol_Cpu' and 'cpu', for instance), Nagiosgrapher.pm wrongly matches services from 'cpu' as '3DEvol_Cpu' ones. Thus, service 3DEvol_Cpu never matches
After replacing inside Nagiosgrapher.pm (subroutine get_ngrapherdef):
@out = grep $service =~ m/$_->service_name}/i,
@out
by
@out = grep $service eq $_->{service_name},
@out
it seems to solve the conflict
The Ngraph.log file before the change, showed:
2008-12-03 09:45:47 REGEX: 6 blocks for '3DEvol_Cpu' found.
and after it:
2008-12-03 09:45:47 REGEX: 3 blocks for '3DEvol_Cpu' found.
Now, the service has matched, and the rrd database has been created
I think this was done on purpose. I had the same problem and I found the solution in some release notes.
To fix, put a ^ in front of the service_name in the .ncfg file. You will get the precise matches you want.
Example:
define ngraph{
service_name ^Current Load
...
Cheers,
James