[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
TRACKMAX feature in 4.3.0b3 - help/info wanted
- To: "xymon (at) xymon.com" <xymon (at) xymon.com>
- Subject: TRACKMAX feature in 4.3.0b3 - help/info wanted
- From: Stephen <Stephen.Mullin (at) usa.net>
- Date: Mon, 29 Nov 2010 16:54:38 -0500
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
- Z-usanet-msgid: XID619okCV3O5968X38
First, thanks for the new release!
I ask for more detail and maybe procedural examples to the TRACKMAX
feature. Built-in TRACKMAX is something I hope will solve the beating
I've been taking.
QUESTIONS:
-"This only works for the NCV backend" .... does this mean only the
addition client tests we add, not the CPU/Mem/vmstat built-ins ?
-Do we have to loop through out RRD files and resize, it it advisable to
do so? (I'm thinking I should)
-Do we have to loop through our RRD files and mod settings to match/sync
with TRACKMAX settings?
The referenced link to a note and discussion don't work, but I did find
some discussions, and sorry to say I wouldn't be able to figure out what
to do from them. My goal is to have 60days of detailed data without too
much granularity loss or smoothing. I got space and plenty of
horsepower. Anything to get the suits off my back about the "bad data"
(their words!).
Thanks,
-Steve
==============================================================