Comments (8)
brian-brazil
commented on May 27, 2024
1
The default is doing some things that can't be done with just one rule (and also handles some escaping issues), several rules are required if you're doing things more specifically.
from jmx_exporter.
brian-brazil
commented on May 27, 2024
Can you give an example of what you're trying to do?
from jmx_exporter.
automaticgiant
commented on May 27, 2024
i think i know what they are talking about. i want something like that.
the default pattern seems to extract any/all/arbitrary labels from domain<beanpropertyName1=beanPropertyValue1, beanpropertyName2=beanPropertyValue2, ...><key1, key2, ...>attrName: value however, if you would like to set up a consistant naming mapping from bean objectName to metric name, you have to cover all desired labels in your pattern. i've been unable to come up with a way to write a rule that can do so while preserving the default rule's ability to get all the labels.
from jmx_exporter.
automaticgiant
commented on May 27, 2024
i was also (due to quitting early probably) unable to find where in the source the default behavior was defined. a pointer would be appreciated.
i'd really like to be able to reproduce default behavior in a config and tweak it. that might satisfy @BarthV as well.
so are you suggesting universally emulating default behavior is possible with a multiple rules?
from jmx_exporter.
brian-brazil
commented on May 27, 2024
so are you suggesting universally emulating default behavior is possible with a multiple rules?
Mostly. In practical terms you should almost always be able to produce a good config for a given server.
from jmx_exporter.
automaticgiant
commented on May 27, 2024
i'm interested in a "universal"-ish config, instead of having to set up a config for each jmx app.
we are kafkaing right now, presumably zookeeper, mirrormaker, nifi, etc to follow...
my main complaint is finding a solution to the metric name and tag setup for instances where you have a bunch of attributes and it explodes the metric namespace with them.
otherwise, default rule would work fine.
have:
#kafka_server_BrokerTopicMetrics_OneMinuteRate{name="BytesOutPerSec",topic="SYSLOG",} 3.0799494822146203
#kafka_server_BrokerTopicMetrics_OneMinuteRate{name="FailedFetchRequestsPerSec",topic="SYSLOG",} 0.0
#kafka_server_BrokerTopicMetrics_OneMinuteRate{name="BytesInPerSec",topic="SYSLOG",} 1.4507932500151888
#kafka_server_BrokerTopicMetrics_OneMinuteRate{name="BytesRejectedPerSec",topic="SYSLOG",} 0.0
#kafka_server_BrokerTopicMetrics_OneMinuteRate{name="TotalFetchRequestsPerSec",topic="SYSLOG",} 63.990540940470744
#kafka_server_BrokerTopicMetrics_OneMinuteRate{name="FailedProduceRequestsPerSec",topic="SYSLOG",} 0.0
#kafka_server_BrokerTopicMetrics_OneMinuteRate{name="MessagesInPerSec",topic="SYSLOG",} 0.010284049118568367
#kafka_server_BrokerTopicMetrics_OneMinuteRate{name="TotalProduceRequestsPerSec",topic="SYSLOG",} 0.010284049118568367
#kafka_server_BrokerTopicMetrics_FiveMinuteRate{name="BytesOutPerSec",topic="SYSLOG",} 7.914210031726753
#kafka_server_BrokerTopicMetrics_FiveMinuteRate{name="FailedFetchRequestsPerSec",topic="SYSLOG",} 0.0
#kafka_server_BrokerTopicMetrics_FiveMinuteRate{name="BytesInPerSec",topic="SYSLOG",} 2.8756598718384767
#kafka_server_BrokerTopicMetrics_FiveMinuteRate{name="BytesRejectedPerSec",topic="SYSLOG",} 0.0
#kafka_server_BrokerTopicMetrics_FiveMinuteRate{name="TotalFetchRequestsPerSec",topic="SYSLOG",} 75.86600439041331
#kafka_server_BrokerTopicMetrics_FiveMinuteRate{name="FailedProduceRequestsPerSec",topic="SYSLOG",} 0.0
#kafka_server_BrokerTopicMetrics_FiveMinuteRate{name="MessagesInPerSec",topic="SYSLOG",} 0.016103353485893434
#kafka_server_BrokerTopicMetrics_FiveMinuteRate{name="TotalProduceRequestsPerSec",topic="SYSLOG",} 0.016103353485893434
#kafka_server_FetcherLagMetrics_Value{name="ConsumerLag",clientId="ReplicaFetcherThread-0-4",topic="SYSLOG",partition="4",} 0.0
#kafka_server_FetcherLagMetrics_Value{name="ConsumerLag",clientId="ReplicaFetcherThread-0-2",topic="SYSLOG",partition="7",} 0.0
#kafka_server_FetcherLagMetrics_Value{name="ConsumerLag",clientId="ReplicaFetcherThread-0-4",topic="SYSLOG",partition="9",} 0.0
#kafka_server_FetcherLagMetrics_Value{name="ConsumerLag",clientId="ReplicaFetcherThread-0-5",topic="SYSLOG",partition="0",} 0.0
#kafka_server_FetcherLagMetrics_Value{name="ConsumerLag",clientId="ReplicaFetcherThread-0-4",topic="SYSLOG",partition="3",} 0.0
#kafka_server_FetcherLagMetrics_Value{name="ConsumerLag",clientId="ReplicaFetcherThread-0-5",topic="SYSLOG",partition="8",} 0.0
#kafka_server_BrokerTopicMetrics_FifteenMinuteRate{name="BytesOutPerSec",topic="SYSLOG",} 9.285483891560915
#kafka_server_BrokerTopicMetrics_FifteenMinuteRate{name="FailedFetchRequestsPerSec",topic="SYSLOG",} 0.0
#kafka_server_BrokerTopicMetrics_FifteenMinuteRate{name="BytesInPerSec",topic="SYSLOG",} 3.078354766954514
#kafka_server_BrokerTopicMetrics_FifteenMinuteRate{name="BytesRejectedPerSec",topic="SYSLOG",} 0.0
#kafka_server_BrokerTopicMetrics_FifteenMinuteRate{name="TotalFetchRequestsPerSec",topic="SYSLOG",} 83.79707100258736
#kafka_server_BrokerTopicMetrics_FifteenMinuteRate{name="FailedProduceRequestsPerSec",topic="SYSLOG",} 0.0
#kafka_server_BrokerTopicMetrics_FifteenMinuteRate{name="MessagesInPerSec",topic="SYSLOG",} 0.015124558666446455
#kafka_server_BrokerTopicMetrics_FifteenMinuteRate{name="TotalProduceRequestsPerSec",topic="SYSLOG",} 0.015124558666446455
want something more like:
#kafka_server:BrokerTopicMetrics{attribute="Count...
#kafka_server:BrokerTopicMetrics{attribute="MeanRate...
#kafka_server:BrokerTopicMetrics{attribute="OneMinuteRate...
#kafka_server:BrokerTopicMetrics{attribute="FiveMinuteRate...
#kafka_server:BrokerTopicMetrics{attribute="FifteenMinuteRate...
basically, i just want to move the attribute into a tag, not as part of the metric name.
from jmx_exporter.
automaticgiant
commented on May 27, 2024
sorry if i'm hijacking the issue or if it's a different issue. depending on solution, it could be the same issue. @BarthV
it's definitely not the stated issue... :(
i guess i should make a new one?
if the solution were as follows, it would maybe do both:
provide a way to utilize default behavior (automatically grabbing labels), but tweak (move attribute to a label/add new labels to detected labels)
from jmx_exporter.
brian-brazil
commented on May 27, 2024
i'm interested in a "universal"-ish config, instead of having to set up a config for each jmx app.
That's unlikely to happen, JMX usage is nowhere near standard enough to allow for that. That's why it's all regexes, there's no common structure.
basically, i just want to move the attribute into a tag, not as part of the metric name.
Those belong as part of the metric name, though of those you really only want the Count and Value.
from jmx_exporter.
Related Issues (20)
- How can I send metrics simultaneously for kafka metrics and for kafka connect HOT 1
- File descriptors opened by jmx exporter getting stuck in CLOSE_WAIT state HOT 33
- Logging of jmx and alerts what all it can monitor HOT 1
- difference between metrics in jmx exporter HOT 1
- Duplicate metrics with NaN HOT 1
- Drop support for Java 8 HOT 8
- Blacklisting Percentile Metrics HOT 3
- Metrics for a specific process HOT 6
- the problem of getting data from multiple replicas under Kubernetes deployment controller and how to distinguish replica labels based on podname HOT 2
- JMX exporter high memory usage. HOT 3
- have any metric about jvm GC Pause? HOT 3
- Proposal: attributes as metrics & extra metrics HOT 7
- Can't add metrics to blacklistObjectNames HOT 6
- Plan for release with Prometheus Client 1.x? HOT 1
- no main manifest attribute, in jmx_prometheus_javaagent-0.19.0.jar HOT 1
- Hazelcast Metrics are not showing HOT 2
- Remote jmx has enabled SSL. How to configure jmx-exporter for verification? HOT 13
- Ability to use lowercaseOutputName in particular rules HOT 4
- jmx exporter inside Confluent Kafka broker container HOT 2
- After applying JMX filtering pattern, it takes 23 secs to scrape the metrics, is it expected behaviour? HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jmx_exporter.