On 5/7/10 9:37 AM, Brad Nicholes wrote: > > This is the process which packages a metric into a very small packet which > can be passed between systems safely.
Apologies for barging into this discussion, but I've been working on getting used to the modules features of ganglia this week and this caught my eye. In the past I've used gmetric to get some auditing information from our systems. For example, space and inode usage on specific user-owned filesystems. My script collects this list of mounts, delimits it, then uses gmetric to dump it into the xml tree for collection at a central location. I'm aware ganglia is intended to be performance monitoring software, but it's always been so good at shipping data around it's hard to resist using it for more than just metrics. At any rate, as we prepare for our upgrade to ganglia 3, I discovered that submitting strings via the python module interface is limited to 32 characters.. anything longer produces some odd behavior in the xml tree. I was able to increase this maximum by adjusting the MAX_G_STRING_SIZE in gm_value.h, but your comment about small packets and safety make me question whether this is wise. Are there risks to this I am unaware of? If I have to pass arbitrary non-graphable data from my machines to a central host, should I continue to use gmetric? If so, what does gmetric do differently that allows longer strings than gmond does? ------------------------------------------------------------------------------ _______________________________________________ Ganglia-general mailing list Ganglia-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-general
