-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today, Federico Sacerdoti wrote forth saying...
> From: Federico Sacerdoti <[EMAIL PROTECTED]> > To: matt massie <[EMAIL PROTECTED]> > Cc: Ganglia Developers <[email protected]> > Date: Fri, 30 May 2003 13:53:35 -0700 > Subject: Re: [Ganglia-developers] wire format > > > On Friday, May 30, 2003, at 12:57 PM, matt massie wrote: > > > /* An explicit message from an unregistered source (gmetric) (85 > > bytes) */ > > (1()((cpu) float % gauge)((user 10.0)(system 10.0)(nice 10.0)(idle > > 90.0))) > > > > 24 bytes larger because we have to since the metric attribute > > information. > > > > /* A super explicit message with explicit host info (104 bytes) */ > > (1("compute-node-0-0" "10.0.0.5") > > ((cpu) float % gauge) > > ((user 10.0)(system 10.0)(nice 10.0)(idle 90.0)) > > ) > > I like it. A few questions. Why the quotes around the host and ip. Why > are we changing the "slope" terminology? positive, negative, both, zero > make sense, and we all understand them. The term "gauge" is hard to > spell :) and I dont immediately remember what it is supposed to mean. the quotes are not necessary actually.. not sure why i put them. we only need quotes if we have whitespace characters in there. we can use the slope terminology instead. the reason i wanted to use "trend" was that it's more general and would allow us to specify more processing strategies as we like. with "slope" there are only 4 possibilities really. i took the names "counter" and "gauge" from rrdtool since it is our tool of choice for saving historical (trend) data. > Also, what about a metric precision attribute? An int that specifies the > number of decimal places for a float. i "think" (not sure) that the right place for that is in a frontend module. the backend (gmond/gmetad) will concentrate on collecting the data and exporting it to client.. the formatting stuff (how to display a float) should be a matter of the client. again.. i'm not certain about this and am open to suggestions.. i'm thinking we would have backend modules in C and frontend "modules" in PHP. these files would describe how to format and display the content provided by the backend. i was thinking it could be a part of "conf.php" or something like that (seperate files might be too much i/o.. in a database might be too heavy and make installation more complex.. need to think more about it). there of course would be intelligent defaults if a developer only wanted to collect data and not worry so much about how it is formatted. - -matt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+19HzVmIXr0CKtmERAly6AJ9FDhPmkyO/5pJ9gF7FweyNL+5ZGwCfcDgX PfNspIB0J2TX8hLT0tD9ppw= =Ll+I -----END PGP SIGNATURE-----
