[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] Xymon hosts database.
- To: <hobbit (at) hswn.dk>
- Subject: RE: [hobbit] Xymon hosts database.
- From: "Ward, Martin" <Martin.Ward (at) colt.net>
- Date: Wed, 1 Jul 2009 11:45:37 +0100
- References: <OFA6979B4A.8294B24A-ONCA2575E5.0082791A-CA2575E6.0001BAF7 (at) dpi.nsw.gov.au> <BAY138-W17D9B2123AE08CB53048FB9F2E0 (at) phx.gbl> <200907011034.05210.bgmilne (at) staff.telkomsa.net> <13D17C28DB14415B903D16153C7B1551 (at) behemoth>
- Thread-index: Acn6JzLRuM6nPjvxQ+ahjZAACRG9MAADoFJgAAB9ENA=
- Thread-topic: [hobbit] Xymon hosts database.
> -----Original Message-----
> From: David Peters [mailto:davidp (at) electronf.com]
> Sent: 01 July 2009 11:26
> To: hobbit (at) hswn.dk
> Subject: RE: [hobbit] Xymon hosts database.
>
> What I have is a database front end, database and extraction script to
> hobbit. The database was written from the viewpoint of storing data
> about
> all the hosts that would end up in hobbit. It was always written to be
> our
> hobbit data source and as such has that in mind.
>
> The model is solid in terms of operations managing the data but
> provides
> auditing and control.
>
> The downside is that it is written in access because that is what the
> manager wanted and I am but a lowly contractor.
>
> I am just a bit wary of trying to put too much into a configuration
> tool.
If I may suggest, just start with porting your Access database to MySQL.
You might even be able to add hooks in to MS Access to point to the
MySQL server and run your extraction scripts on the MySQL data (although
that may be more effort than it's worth, I am not skilled in Access so
don't know what effort will be involved). After you have the MySQL DB
you can convert the extraction scripts, that would probably be the
simplest task in this project.
After that it's just coding the Perl/PHP scripts to access and maintain
the database.
You could help yourself and others by putting the SQL code into a
stand-alone module, making it easier to port to other SQL servers.
KISS and do it a step at a time. Keep us informed and we will help where
we can.
> What I hate about hobbit and trying to sell it is that its host
> configuration is pretty ordinary.
>
Yeah, but ordinary isn't necessarily bad, at least not for a couple of
dozen servers. It's only when you get to hundreds of servers that it
starts to become awkward.
*************************************************************************************
The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way.
The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security (at) colt.net and delete the message and any attachments without retaining any copies.
Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses.
No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party.
Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.