[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] Metrics Report
- To: <hobbit (at) hswn.dk>
- Subject: Re: [hobbit] Metrics Report
- From: "Christopher Bodnar" <christopher_bodnar (at) glic.com>
- Date: Thu, 11 Feb 2010 11:46:35 -0500
- Importance: normal
- Priority: normal
- References: <OFE665A0F8.6453ED68-ON852576C5.007387A3-852576C5.0074F165 (at) glic.com> <201002100841.51597.bgmilne (at) staff.telkomsa.net>
- Thread-index: AcqrOclZruCioYOORauhqWcl0w3pAQ==
Thanks Buchan,
I found that there is a RAM-Multi graph definition defined, which will be
sufficient for my needs right now.
Chris Bodnar, MCSE
Systems Engineer
Distributed Systems Service Delivery - Intel Services
Guardian Life Insurance Company of America
Email: christopher_bodnar (at) glic.com
Phone: 610-807-6459
Fax: 610-807-6003
From: Buchan Milne <bgmilne (at) staff.telkomsa.net>
To: hobbit (at) hswn.dk
Cc: "Christopher Bodnar" <christopher_bodnar (at) glic.com>
Date: 02/10/2010 02:45 AM
Subject: Re: [hobbit] Metrics Report
On Tuesday, 9 February 2010 22:17:19 Christopher Bodnar wrote:
> I'm relatively new to Hobbit. I've successfully created a CPU metrics
> report for multiple hosts by modifying the URL, specifically by adding
> additional &HOST= entries and modifying the start and end times to
target
> the report. This has worked successfully for CPU, but I would like to do
> the same thing for RAM. It doesn't seem to work, having multiple &HOST=
> entries if the service is =memory. The ideal result will be a report
that
> just shows the "real" bar graph, not the swap bar graph, for each of the
> hosts I need.
>
>
>
> Anyone have some suggestions regarding this?
Add a memory-multi graph definition in hobbitgraph.cfg, based on the
existing
memory graph definition, but with similar changes as between the la and
la-
multi graph definitions.
Regards,
Buchan
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk
-----------------------------------------
This message, and any attachments to it, may contain information
that is privileged, confidential, and exempt from disclosure under
applicable law. If the reader of this message is not the intended
recipient, you are notified that any use, dissemination,
distribution, copying, or communication of this message is strictly
prohibited. If you have received this message in error, please
notify the sender immediately by return e-mail and delete the
message and any attachments. Thank you.