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

Structured metricset for Jolokia Module #3585

Closed
ruflin opened this issue Feb 14, 2017 · 3 comments
Closed

Structured metricset for Jolokia Module #3585

ruflin opened this issue Feb 14, 2017 · 3 comments
Labels

Comments

@ruflin
Copy link
Contributor

ruflin commented Feb 14, 2017

In #3570 a dynamic jmx metricset was implemented for Jolokia. There are common values like memory across most jolokia installation. One or several metricsets should be created for the Jolokia module which contain these fields. This allows to simplify the configuration for basic cases and to have shipped dashboards with it as all fields are known in advance.

@rhuss
Copy link

rhuss commented Feb 14, 2017

A good starting point could be https://github.com/rhuss/jmx4perl/tree/master/config which holds the definition for some common Nagios checks. The contain also the MBean and attribute name for some metrics to measure. Especially in memory.cfg and threads.cfg should be applicable to any JVM.

However, memory is a bit tricky, since e.g. the MBean name for the garbage collector statistics depend on the configured garbage collector and the JVM version used.

@ruflin
Copy link
Contributor Author

ruflin commented Feb 16, 2017

Thanks for sharing these configs. For the memory we could make the MBean name configurable and have one as default. Like this it would work for different configs and JVM I hope.

On a different note: I had a look at https://github.com/rhuss/jmx4perl/blob/master/config/jboss.cfg and it seems in there you also define critical and warning. I assume that is when you get a message from the system? In Elastic-Stack terms that is similar to a watcher config?

Did you have a chance to try out the jmx module? Would really like to get some feedback on it :-)

@botelastic
Copy link

botelastic bot commented Jul 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the Stalled label Jul 8, 2020
@botelastic botelastic bot closed this as completed Aug 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants