-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collector for MapR Hadoop node metrics. #281
Conversation
- provide all metric names - change 'capacity' to 'mfs'
… the metrics directory
ca833b7
to
1298bd0
Compare
I moved this to 1.3.1 as I don't have a good way to test it. @vicenteg would you be able to pull down this after the changes I made and test it? I'd really like to see a text file attached of the new metrics. I typically get this by dumping the output of one run and piping to:
You can run a single collector like this: `bash -c "PYTHONPATH=$PYTHONPATH:./collectors/lib:./ python collectors/0/mapr_metrics.py"`` I apologize if you already know all this, just trying to be helpful! :) |
I appreciate the help! Is there a naming convention you prefer for metrics? On Tue, Feb 16, 2016 at 10:02 AM, Jonathan Creasy notifications@github.com
|
Well, very generically I use the metric name for a metric and tags create a specific instance of that metric. Ex name: net.io Ex tags: net.io direction=in host=hostname interface=interfacename |
Sorry for the long delay. The collector with your changes does work against my MapR v5.1 cluster. Here's the list of metrics (I had to modify your awk pipeline to print $1, hope the below is what you were expecting):
|
Fixes #196