Dirk,
RRDtool is a kind of database library with utilities to manipulate the data. You
create a database to hold e.g. 100 samples for a data source, one every 5 minutes. In
the same file it can also keep derived data, such as average, minimum, maximum. These
values the tool will calculate itself when you add data to the database. For the
derived tables you also configure how many samples you want to keep. This way you can
keep the values for a day, a week, a month. The database always stays the same size,
because the sample slots are reused (sample 101 will be stored in position 1).
The graphs are created by RRDtool when you give it a "graph" command.
The data it stores must of course be numeric. To feed data to the database, you give a
command like: rrdtool update <database_file> <timestamp>:<value>
The timestamp should be in unix time (seconds since 1/1/1970). If there is no value
for a certain time, the value should be "U".
Now, what SA data would be interesting for graphing? Anything numeric I would say: the
respons time of a protocol check, the diskspace you get from a diskspace check, the
value you get from a perfmon of snmp check,...
Most of these values can be found in the interchange file, but there are always extras
such as the unit (100 MB, 5 ms) and I'm not sure SA always uses the same unit. Another
problem is that SA puts a value in the interchange file when a check is not performed.
To link it with a kind of interchange file, the format should be something like
<uid>,<value_id>,<timestamp>,<value>
Where the <value> is always numeric, without a unit, always the same unit (bytes for
anything with memory, ms for anything with time).
When there's no result, the value should be "U".
<value_id> would be a unique ID that SA would have to create to make the difference
between the result of the check (e.g. 300 MB free) and the time it took (35 ms). E.g.
the uid and "A" for the result, the uid and "B" for the time.
105, 105A, 920808000, 300000000 -> this is the free diskspace
105, 105B, 920808000, 15 -> this is the time it took
The <uid> is needed to select the database (I would create a database for each check
with the uid as filename).
Then after this export an external command could feed the data to rrdtool.
Johan
-----Original Message-----
From: Dirk Bulinckx [mailto:[EMAIL PROTECTED]
Sent: maandag 27 oktober 2003 17:45
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] Dreaming of features for version 5.....
What kind of data is needed and how is it stored?
"who" creates weekly/monthly/....averages? Is that RDD that does it or
is that something that they app that adds the info should do?
dirk.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dewachter Johan
Sent: Mon Oct 27 5:27 PM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] Dreaming of features for version 5.....
My Servers Alive dream would be a way to feed SA's results into RRDtool.
http://people.ee.ethz.ch/~oetiker/webtools/rrdtool/
=== from the site:
If you know MRTG, you can think of RRDtool as a reimplementation of
MRTGs graphing and logging features. Magnitudes faster and more flexible
than you ever thought possible
RRD is the Acronym for Round Robin Database. RRD is a system to store
and display time-series data (i.e. network bandwidth, machine-room
temperature, server load average). It stores the data in a very compact
way that will not expand over time, and it presents useful graphs by
processing the data to enforce a certain data density. It can be used
either via simple wrapper scripts (from shell or Perl) or via frontends
that poll network devices and put a friendly user interface on it. ===
This would give you daily, weekly, monthly graphs of diskspace, CPU use,
...
RRDtool is open source, free, runs on Windows and Unix and there are
other commercial products using it (hint).
Johan
-----Original Message-----
From: Michael Shook [mailto:[EMAIL PROTECTED]
Sent: maandag 27 oktober 2003 16:16
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] Dreaming of features for version 5.....
Well, I did say I was dreaming..... :-)
Mike
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
