Skip to content
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

Merged
merged 10 commits into from Sep 18, 2020
Merged

Collector for MapR Hadoop node metrics. #281

merged 10 commits into from Sep 18, 2020

Conversation

johann8384
Copy link
Member

Fixes #196

@johann8384 johann8384 added this to the 1.3.0 milestone Feb 16, 2016
@johann8384 johann8384 self-assigned this Feb 16, 2016
@johann8384 johann8384 changed the title Issue 196 Collector for MapR Hadoop node metrics. Feb 16, 2016
@johann8384 johann8384 modified the milestones: 1.3.1, 1.3.0 Feb 16, 2016
@johann8384
Copy link
Member Author

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:

awk '{print #2}' | sort | uniq

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! :)

@vicenteg
Copy link
Contributor

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
wrote:

I moved this to 1.3.1 as I don't have a good way to test it. @vicenteg
https://github.com/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:

awk '{print #2}' | sort | uniq

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! :)


Reply to this email directly or view it on GitHub
#281 (comment).

@johann8384
Copy link
Member Author

Well, very generically I use the metric name for a metric and tags create a specific instance of that metric.

Ex name:

net.io
docker.memory.used

Ex tags:

net.io direction=in host=hostname interface=interfacename
docker.memory.used type=rss
docker.memory.used type=cache

@johann8384 johann8384 modified the milestones: 1.3.1, 1.3.2 Mar 16, 2016
@vicenteg
Copy link
Contributor

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):

mapr.cpus.CPUIDLE
mapr.cpus.CPUIOWAIT
mapr.cpus.CPUTOTAL
mapr.disks.READBYTES
mapr.disks.READOPS
mapr.disks.WRITEBYTES
mapr.disks.WRITEOPS
mapr.memory.used
mapr.mfs.available
mapr.mfs.used
mapr.network.BYTESIN
mapr.network.BYTESOUT
mapr.network.PKTSIN
mapr.network.PKTSOUT
mapr.rpc.count
mapr.rpc.inbytes
mapr.rpc.outbytes

@johann8384 johann8384 modified the milestones: 1.3.3, 1.3.2 Jul 6, 2016
@johann8384 johann8384 merged commit 2448961 into master Sep 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants