Question according retention.dat
Posted: Wed Jan 19, 2011 6:07 am
Good morning,
we have a problem with reading current nagios status information over "MK Livestatus" (http://mathias-kettner.de/checkmk_livestatus.html)
All works great, except the "alias" field from host objects. If you change the alias in the nagios configuration it is displayed correctly on the webinterface, but livestatus returns the old (initial) value.
So we started to find the cause of this behavior and found out, that the alias is also never beeing updated in the retention.dat file. The alias is only updated, if you delete the retention.dat file.
Well we dont think livestatus uses the retention.dat file, but maybe is there a internal (nagios) datastructure which does not get the alias field updated.
Anyway, the information is not beeing updated in the retention.dat, is this working as intended ?
>> Our Test Setup is running with the newest Nagios® Core⢠3.2.3, just with one host and one service
>> We also unloaded the livestatus broker module, to make sure it does inflict the retention.dat generation
>> I added our test configuration as attachment
Kindly regards,
Lukas
we have a problem with reading current nagios status information over "MK Livestatus" (http://mathias-kettner.de/checkmk_livestatus.html)
All works great, except the "alias" field from host objects. If you change the alias in the nagios configuration it is displayed correctly on the webinterface, but livestatus returns the old (initial) value.
So we started to find the cause of this behavior and found out, that the alias is also never beeing updated in the retention.dat file. The alias is only updated, if you delete the retention.dat file.
Well we dont think livestatus uses the retention.dat file, but maybe is there a internal (nagios) datastructure which does not get the alias field updated.
Anyway, the information is not beeing updated in the retention.dat, is this working as intended ?
>> Our Test Setup is running with the newest Nagios® Core⢠3.2.3, just with one host and one service
>> We also unloaded the livestatus broker module, to make sure it does inflict the retention.dat generation
>> I added our test configuration as attachment
Kindly regards,
Lukas