Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
I like this thread! It raisedanother thought...=0A(Please ignore me, if I a=
m totally of track
backend=0Aand a webservice. Wouldn't it make sense to take a=0Alook at the =
DB schema used by Merlin & Ninja, or is it=0Atoo heavy? Possibly the same s=
chema could be used and=0Apotentially open for the use of Ninja (the offici=
ally=0A"new" Nagios GUI) without involving Merlin. Don't get=0Ame wrong her=
e. Ireally like Merlin, it rocks, but if=0Ayou do not need allits funtional=
ity a lightweight=0ADB only alternative whould be nice.=0A=0AI realize that=
some information will be missing, but=0Athe potential of code re-use is th=
ere.=0A=0AFor the backend myvote is on SQLite. It supports more=0Aclient ap=
ps any way.=0A=0AI am not the man to judge pros & cons of JSON vs XML.=0ABu=
t if we are talking web services, the client app=0Adoes not need to be a we=
b page. Is JSON suitable for=0Aother client apps as well? Just asking, I do=
n't know.=0A=0A______________________________________________=0ASven-G=F6ra=
n Bergh=0ASystemasis AB=0A______________________________________________=0A=
=0A=0A=0A=0A________________________________=0AFr=E5n: "yann.jouanin.list@i=
ntelunix.fr" =0ATill: Nagios Developers Lis=
t =0ASkickat: tisdag 18 augusti 2009 10=
:27:57=0A=C4mne: Re: [Nagios-devel] XML, JSON, Webservice or something new =
?=0A=0A=0AUsing CDB or SQLite look a good thing for me.=0A=0AI didn't impro=
ved Nagios2JSON a lot cause it's a C CGI and it take long=0A=0Atime to sani=
tize everything.. but if someone wants to help me in improving=0A=0ANagios2=
JSON, then Welcome!=0A=0A=0A=0AAs pointed out Thomas, I also wrote a patch =
to get status.dat directly=0A=0Awriten in JSON but I think the major proble=
m is what ever you want you'll=0A=0Aparse the complete status.dat.=0A=0AHav=
ing a File DB instead of status.dat would be a real way to help in=0A=0Awri=
ting new XML or JSON interface in an easy way. I also did a python=0A=0Asta=
tus.dat parser and rewrite Nagios2JSON with it to test how easy it=0A=0Abec=
omes also with atomic query...=0A=0A=0A=0AYann=0A=0A=0A=0A=0A=0A=0A=0A=0A=
=0A=0A=0A=0A=0AOn Tue, 18 Aug 2009 04:11:09 -0400, Thomas Guyot-Sionnest =0A=0Awrote:=0A=0A> -----BEGIN PGP SIGNED MESSAGE-----=0A=0A>=
Hash: SHA1=0A=0A> =0A=0A> On 17/08/09 10:08 PM, Max wrote:=0A=0A>> Hi Derr=
ick,=0A=0A>> =0A=0A>> On Mon, Aug 17, 2009 at 8:32 PM, local.coder wrote:=0A=0A>>> I am back to writing some code for a new projec=
t involving Nagios. As=0A=0A>>> part of this I need light weight data acces=
s to status.cgi data.=0A=0A>>> Initially I was planning on modding ministat=
us.cgi which I know is not=0A=0A>>> part of the contrib anymore but it is a=
good starting place. At the=0A=0Asame=0A=0A>>> time I looked into the stat=
us of something more standardized. I would=0A=0A>>> prefer to code to a sta=
ndard that we can all get behind. The=0A=0ANagios2Json=0A=0A>>> looks nice =
in that JSON is a basic format and gives me what I need,=0A=0A>>> however t=
he current project is not Version 3+ compliant. I also found=0A=0A>>> the N=
XE addon for XML output but that has not been updated in some=0A=0Atime.=0A=
=0A>> =0A=0A>> The only problem with the current nagios2json is that you ca=
nnot do=0A=0A>> discrete queries of hosts/services etc, so not quite ready =
for AJAX=0A=0A>> UIs.=0A=0A> =0A=0A> I like the JSON patch as it implement =
cleanly a different way of writing=0A=0A> status data to status files. Howe=
ver I had in mind doing something=0A=0A> similar but with CDB. CDB is a sma=
ll and very efficient read-only=0A=0A> database format that has a C and PHP=
(among others) APIs. It store only=0A=0A> key-values and it is designed to=
be written once and acceded read-only;=0A=0A> just as status.dat works cur=
rently. OTOH, unlike status.dat it could be=0A=0A> qu
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]