Adding support for JMX operation calls. #13
Conversation
Some products expose JMX data through operation calls. This change adds support for calling JMX operations (also with arguments, if needed), by parsing a new configuration property named `operations` and adding the dedicated code for these calls. `operations` is an array of jmx operation, where a jmx operation is defined by its name and an array of arguments.
|
Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then say 'jenkins, test it'. |
|
As I committed for another user (the real author of the code change), I don't know which one of us must sign the CLA... Can someone clarify this ? Thanks. |
|
What's the prospect for this feature? |
|
Any chance of this getting revived? Be extremely useful feature as our vendor app has significant quantity operations exposed. |
|
This plugin needs a community maintainer. Any takers? |
|
Perhaps, only issue is time available. Second issue, primarily Java not ruby (or jruby). Need to think about it. |
|
@GvD49 If you want to rewrite the plugin in Java, you can, as long as it maintains the same basic functionality it currently has. You could look at the new beats input plugin for some guide to writing a plugin in Java, since the beats input plugin was recently rewritten in Java. |
|
Well, java in part at least, since it's using Netty. |
|
@untergeek ping me directly, but I am interested in doing this as a maintainer. |
|
@GvD49 thanks for your request, and apologize for the delay. I'd love to chat with you via email. |
Some products expose JMX data through operation calls. This change adds support for calling JMX operations (also with arguments, if needed), by parsing a new configuration property named
operationsand adding the dedicated code for these calls.operationsis an array of jmx operation, where a jmx operation is defined by its name and an array of arguments.