z

Commercial Support Clients: Clients with support contracts can get escalated support assistance by visiting Nagios Answer Hub. These forums are for community support services. Although we at Nagios try our best to help out on the forums here, we always give priority support to our support clients.

Re: [Nagios-devel] MSQL Tables and log files mis-match in data types, any ideas

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.

Re: [Nagios-devel] MSQL Tables and log files mis-match in data types, any ideas

Postby Guest » Wed Mar 27, 2002 11:24 am

Thanks for pointing this out. The inconsistencies should be fixed,
although its not a huge deal. Changing the DB tables at this point
might be a waste of time, as I plan on dropping native DB support in
version 2.0.


On 27 Mar 2002 at 18:32, Mark Gillett wrote:

> Hi All,
>
> I have been investigating linking some of our in-house tools to Nagios and
> have been working on reading from either the log files or a MySql database
> for retention and status information.
>
> In these explorations I have discovered some 'maybe' inconsistencies in the
> data types used and descriptions of these as below:
>
> I may be missing something or might be just straight dumb on this - has
> anyone else got any ideas ?
>
> in
>
> TABLE hostretention --->
>
>
> last_check int(11)
>
> appears to be a short integer and is described as a time_t since the unix
> epoch in the log-file documentation,
>
> but in
>
> TABLE hoststatus --->
>
> last_check datetime
>
> appears to be a datetime but is still described as a time_t since the unix
> epoch in the log-file documentation
>
> also confusing is that in
>
> TABLE hoststatus --->
>
> time_up bigint(20)
> time_down bigint(20)
> time_unreachable bigint(20)
>
> and are described as no. of seconds elapsed in that state, or since the last
> start of the server, but in
>
> TABLE hostretention --->
>
> time_up int(11)
> time_down int(11)
> time_undreachable int(11)
>
> which is described as no. of seconds elapsed as well.
>
> Am I missing something - does anyone know if there is a reason for this, if
> not should I look at harmonising the database descriptions. Also should we
> think about updating the xdata code to unift the storage between the files
> and the database in terms of data-types.
>
> Also - has anyone written a file to database or database to file conversion
> tool ?
>
> Thanks,
>
>
> Mark Gillett
> IXIF Ltd
> UK NMS Support
>
>
>
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-devel
>



Ethan Galstad,
Nagios Developer
---
Email: nagios@nagios.org
Website: http://www.nagios.org






This post was automatically imported from historical nagios-devel mailing list archives
Original poster: nagios@nagios.org
Guest
 

Return to Open Source Nagios Projects

Who is online

Users browsing this forum: No registered users and 15 guests