[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Some feature notes for monit (XML mock-up)

From: Vlada Macek
Subject: Re: Some feature notes for monit (XML mock-up)
Date: Fri, 09 Jul 2004 17:08:56 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124

Jan-Henrik Haukeland wrote:

> First, thanks for a well presented and constructive email. We need
> new ideas to continue evolve monit. However we are all non-paid
> volunteers and work on monit in our spare time so development tends
> to be interest-based and not always what (others think) are important
> for monit. Suggestions are welcome and suggestions backed up by code
> (patches) are even more welcome and more likely to make it into monit
> :)

Thanks, anyway it's great. I'll try to contribute better in the future. :-)

>> ### Usability: Hashes on the monit command line
>> ### Syntax inconsistence: CERTMD5

Solved. You guys rock! :-) Thank you.

>> ### Access time changed by checks
> 0 Is atime changed by monit?

Yes, I've checked it. Checksum computation changes access time of the file.

>> ### XML output - As I noticed, currently only one kind of monit
>> status page is in XML. More would be great!
> more may come when we continue work on m/monit

Now I think there can be only one XML page with all the status information.

>> - It may be nice to return instant systemwide resource values
>> mentioned once above (uptime since boot, load averages, memory
>> usage, IO, VM...) in XML and perhaps in HTML too.
> Exactly, +1. (HTML though will be the output to monit's web
> interface.). If you would like to propose (write) a suggestion for a
> XML schema it would be interesting. I'm currently stuck with what we
> have.

I'm attaching my XML mock-up. There are some ideas about what could be
in such technical output. I imagine an ideal state, where the
information is generated by one kind of C function for all XML, TEXT and
HTML output. That way the reported dataset will be the same for all
three forms (HTML still divided to pages, XML and TEXT would return all
on one request). But I'm afraid it's not your original goal.

Because of this I've not included detailed <service> information (such
as UID, checksum, free inodes...) in my mock-up, before the feature goal
is pronounced. I would definitely like them there so m/monit (or
anything) could store as much information as it can upon signal for
historical browsing. By signal I mean detecting an alert and
automatically request the status upon change on monit server an store
it. The status does not need to be accessible when the admin finally comes.


<?xml version="1.0" encoding="iso-8859-1"?>
                        <!-- seconds since system boot              -->
                <load>0.03 0.12 0.10 </load>
                        <!-- it's easily parseable everywhere       -->
                        <!-- virtual memory (RAM+swap) usage in %   -->
                        <!-- system clock and XML timestamp         -->
                        <!-- seconds since monit daemon (re)loaded  -->
                        <!-- of the monit binary if available       -->
                                <!-- after all includes             -->
                                <!-- last mtime touch               -->
        <service type="Process">
        <service type="Process">
        <service type="File">
        <service type="File">

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]