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
WildFly 10 example #87
Conversation
--- | ||
lowercaseOutputName: true | ||
lowercaseOutputLabelNames: true | ||
whitelistObjectNames: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given this is a framework, you shouldn't assume only the wildfly objects are of potential interest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So remove the whitelist or did I missunderstand you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd remove it
attrNameSnakeCase: true | ||
name: wildfly_messaging_$2 | ||
labels: | ||
name: $1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Call this queue or topic
labels: | ||
name: $1 | ||
|
||
- pattern: "^jboss.as<subsystem=transactions><>(number_of_.+):" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd not include the number_of_ in the output name. Every metric is the number of something.
Updated with your suggestions, removing the whitelist increases scrape time with ~8x but since it's just an example config i guess that's not a real problem :) |
Thanks! |
@cfrantsen I am trying to get this working with Wildfly 10 without any luck. I am wondering if you have a complete example you could share? The problem is the connection from |
I'm using the jmx_exporter as a java agent when running on WildFly. It requires some fiddling with start parameters to get working, below is an excerpt from the start script I'm using:
|
Thanks Christian! Do you have to specify either Here is a dump of my |
No that should not be needed when running it as a java agent. Have you tried a config file without explicit rules, that should give you a huge amount of metrics back. |
I get much more output, but still nothing about Wildfly/Undertow: gist.github.com/9a8ff4. How do you start your Wildfly? Are you using the standalone.sh command? |
Sorry for bothering; I have made a minimal Wildfly jmx_exporter example using the official Wildfly Docker image and latest version of From the Dockerfile source: ADD jboss-logmanager-2.0.6.Final.jar /opt/jboss/wildfly
ADD jmx_prometheus_javaagent-0.9.jar /opt/jboss/wildfly
ADD prometheus-config.yaml /opt/jboss/wildfly
ENV JAVA_OPTS "-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager \
-Xbootclasspath/p:/opt/jboss/wildfly/jboss-logmanager-2.0.6.Final.jar \
-javaagent:/opt/jboss/wildfly/jmx_prometheus_javaagent-0.9.jar=31500:/opt/jboss/wildfly/prometheus-config.yaml" You can run this yourself using |
We are running 0.7.3.298dcdc here right now so maybe it's a problem with recent versions? Perhaps try an older version and if that works create an issue. |
Thanks a million @cfrantsen 💯 I only tried with v0.8 and v0.9, this is now working perfectly in v0.7! |
Could you perhaps create an issue regarding this as it can be fixed? |
Anyone got this working for Wildfly 8.2.1? Using @cfrantsen's example it dies with the following message.
|
Finally got it working. If anyone else is stumbling on similar issues, remember: the following flags MUST ALL be included in JAVA_OPTS.
Particularly, I was running in circles trying to define JBOSS_MODULES_SYSTEM_PKGS before starting wildfly. By the looks of ... Except, it isn't for some reason.
I successfully tested it with Wildfly-8.2.1.Final and Wildfly-10.1.0.Final. PS: If you have custom-handlers defined for logging, the above will also not work. Some of our installations need to define a custom logger to send logs to a remote graylog server via UDP. With a custom-handler defined, Wildfly's LogManager will not be able to bootstrap ahead of time for JMX Exporter. |
No description provided.