----- Original Message -----
From: "Jay Shaughnessy" <jshaughn(a)redhat.com>
To: rhq-devel(a)lists.fedorahosted.org
Sent: Monday, July 15, 2013 11:34:51 AM
Subject: Re: Storage Node - Disk Space Metric
>
> 1) Should we include both metrics? Overall disk space use & data files disk
> space used? We could only hope that having the two metrics will make it
> easier for users to understand what they are.
I think two metrics is a good idea. We must have a way to easily alert
on a disk space consumption. The Iteration-3
Calculated.PartitionDiskSpaceUsedPercentage metric is useful
information: How much of my used disk space is due to my storage node?
But it's mainly useful to help understand if a disk space issue is or is
not due to the storage node. We need the Iteration-3
Calculated.PartitionDiskSpaceUsedPercentage metric for alerting on
excessive disk space for the storage node partitions. Of course we'd
need two names that describe the distinction. I think both metrics
should be on the same resource as they are related.
If we put the two metrics on the same resource (Cassandra Storage Service) how could we
prevent confusion over the meaning of the two metrics?
How about these two names: Calculated.DataDiskSpaceUsedPercentage &
Calculated.SystemDiskSpaceUsedPercentage
Thank you,
Stefan Negrea