jmx2graphite
jmx2graphite copied to clipboard
Problem with WHITE_LIST_REGEX
We are using jmx2graphite to export MBean metrics from our Ignite Cluster to Grafana. To filter out the number of metrics being exported, we are using WHITE_LIST_REGEX.
-javaagent:/opt/ignite/jmx2graphite-1.5.0-javaagent.jar=GRAPHITE_HOSTNAME=carbon.example.com,SERVICE_NAME=staging.ignite,GRAPHITE_PORT=30023,GRAPHITE_PROTOCOL=tcp,INTERVAL_IN_SEC=30,WHITE_LIST_REGEX=^.*java.lang.*$"
We are able to see the metrics in Grafana and here is the entry from /var/log/syslog
Jan 25 08:14:40 ignite-staging-0 service.sh[10830]: 21/01/25 08:14:40 INFO jmx2graphite.MetricsPipeline: Filtered out 12 metrics out of 28 after white/blacklisting
Now when we modify the WHITE_LIST_REGEX to filter type_Runtime path
-javaagent:/opt/ignite/jmx2graphite-1.5.0-javaagent.jar=GRAPHITE_HOSTNAME=carbon.example.com,SERVICE_NAME=staging.ignite,GRAPHITE_PORT=30023,GRAPHITE_PROTOCOL=tcp,INTERVAL_IN_SEC=30,WHITE_LIST_REGEX=^.*java.lang.type_Runtime.*$
we don't see the metrics for this path in Grafana. This is the entry from /var/log/syslog
Jan 25 09:19:59 ignite-staging-0 service.sh[12960]: 21/01/25 09:19:59 INFO jmx2graphite.MetricsPipeline: Filtered out 28 metrics out of 28 after white/blacklisting
Note: We are sure this path java.lang.type_Runtime exists because we were able to see its values in the first case.
Please help with this issue. Thank you!
I'll try to find time to address this. I was thinking of adding a trace log message with metrics before filtering and after filtering. I'll get back to you on this.
@asafm Any update on this issue? Thank you!
Sorry @vijaynandwani I'm spending a small amount of time on this project. I've spent last portion on being able to do proper release. I hope clear some more time to add that trace message.