|
Nathan and Ken,
On 2/3/15 3:02 PM, Ken McDonell wrote:
On
04/02/15 03:49, Martins Innus wrote:
Hi,
I am starting to work on a ganglia to PCP archive converter ...
OK that sounds like a useful addition.
In this case, if you constructed a pcp archive each day
containingin the previous 24 hours ganglia data, if you didn't
do some
sort of state saving, each metric would start off at a raw
counter value
of zero. Then at some later time, if you wanted to pmlogextract
for a
time period that spanned multiple of these converted logs, you
would get
a discontinuity when these "counters" reset to zero.
Yep. In fact you'd get this discontinuity and a <mark>
record at each archive boundary, independent of the counters being
reset, because each pmlogger invocation starts a new session with
pmcd and this may be because pmcd has been restarted or the
machine rebooted, both of which would cause PMDA data to be reset.
So I don't think this is any different to the status quo.
Thanks for the feedback. I'm done with the bulk of the work and now
am getting a little tripped up on handling times/timezones. I found
this conversation here:
http://comments.gmane.org/gmane.comp.sysutils.pcp/3003
With the comment:
"The hostname and timezone will default to the local host, but can
be
explicitly set after pmiStart() by calling pmiSetHostname() or
pmiSetTimezone().
"
But the examples I looked at (mover2pcp, iostat2pcp) explicitly set
the timezone to UTC and only change it based on the presence of a
command line option, ignoring, I think, what may be configured on
the local host. Is that the way to go for default options? In our
use case we'd always be setting an option for local time.
The ganglia stats are already in unix time, so no conversion is
needed there, but this would affect parsing start end/times, etc I
think.
Thanks
Martins
|
|