Currently, gmetad.conf allows you to set the RRA configuration for new RRD files it creates. You define a bunch of RRAs for the time ranges and resolutions you want, and every new metric created will have those RRAs.
You can define high resolution RRAs that last a long time, if you want to be able to view historical data in greater detail, but there's a tradeoff: it takes more space. There are really only a small subset of metrics that I'd really like to view in greater detail further back in time. The amount of space needed to store long-term high resolution RRAs for just those metrics may not be prohibitive. However, there's no way to do that. Whatever RRAs I define in gmetad.conf will be used for ALL new metrics, and we use a lot of custom metrics. Each new database server, for example, will have about ~200 metrics, because we track processes per-user and per-host. Most of these are ones that I don't need the longer-term hi-res data. It would be a really nice feature in a future Ganglia version to be able to have RRD "classes" for metrics, so you could arbitrarily define which sets of metrics get which RRA config. Has anyone found a clever way to define one set of RRAs for "key" metrics, and another set of RRAs for all other metrics? Or patched gmetad to support this? -- Cos ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
