Replies: 2 comments 1 reply
-
|
have you set |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Yep `monitoring: -- Expose JMX metrics with jmx_exporter https://github.com/prometheus/jmx_exporterexposeJmxMetrics: true -- JMX exporter init container configurationjmxExporterInitContainer: -- Annotations added to the jmx servicejmxServiceAnnotations: {} -- Fetch jmx_exporter jar from the image. If set to false make sure to manually copy the jarto shared home and provide an absolute path in jmxExporterCustomJarLocationfetchJmxExporterJar: false -- Image repository with jmx_exporter jarjmxExporterImageRepo: bitnami/jmx-exporter -- Image tag to be used to pull jmxExporterImageRepojmxExporterImageTag: 1.0.1 -- Port number on which metrics will be availablejmxExporterPort: 9090 -- JMX exporter port typejmxExporterPortType: ClusterIP -- Location of jmx_exporter jar file if mounted from a secret or manually copied to shared homejmxExporterCustomJarLocation: "/var/atlassian/application-data/shared-home/jmx_prometheus_javaagent-1.0.1.jar" -- Custom JMX config with the rulesjmxExporterCustomConfig: {} rules:- pattern: ".*"` |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed there's config for requests/limits in the monitoring section, suggesting there's supposed to be a pod for running the jmx exporter? However even though I have no sync errors, I don't see anything trying to launch a pod for jmx exporting, or am I getting it wrong as to how it's supposed to work?
Beta Was this translation helpful? Give feedback.
All reactions