Add examples of Apache Ignite 2.6.0 basic JMX metrics #319
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,80 @@ | ||
| lowercaseOutputLabelNames: true | ||
| lowercaseOutputName: true | ||
| rules: | ||
| # Apache Ignite provide runtime information on a cluster. Keep in mind that there will be a certain | ||
| # network delay (usually equal to metrics update delay). | ||
| # | ||
| # see https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cluster/ClusterMetrics.html | ||
| - pattern: "^org.apache<clsLdr=(.+), group=Kernal, name=(ClusterMetrics.*)><>(HeapMemory.*):" | ||
| name: ignite_$1_$2_heap_bytes | ||
| help: Ignite cluster amount of heap memory in bytes | ||
|
There was a problem hiding this comment. If you know it's in bytes, append _bytes to the name There was a problem hiding this comment. Agree. Added. JVM metrics used as an example. |
||
| labels: | ||
| attr: $3 | ||
|
There was a problem hiding this comment. Metric names should be in the name There was a problem hiding this comment. This wasn't done, all these attrs should be in the metric name. |
||
| type: GAUGE | ||
| - pattern: "^org.apache<clsLdr=(.+), group=Kernal, name=(ClusterMetrics.*)><>(NonHeapMemory.*):" | ||
| name: ignite_$1_$2_nonheap_bytes | ||
| help: Ignite cluster amount of non-heap memory in bytes | ||
| labels: | ||
| attr: $3 | ||
| type: GAUGE | ||
| - pattern: "^org.apache<clsLdr=(.+), group=Kernal, name=(ClusterMetrics.*)><>(.*Jobs):" | ||
| name: ignite_$1_$2_job | ||
| help: Ignite cluster job detalization | ||
| labels: | ||
| attr: $3 | ||
| # Apache Ignite durable memory can be monitored via data region metrics which will help track overall | ||
| # memory utilization and measure its cluster performance. | ||
| # | ||
| # see https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/mxbean/DataRegionMetricsMXBean.html | ||
| - pattern: "^org.apache<clsLdr=(.+), group=DataRegionMetrics, name=(.+)><>(.*Pages|AllocationRate):" | ||
| name: ignite_$1_$2_pages | ||
| help: Ignite durable memory pages currently loaded in RAM | ||
| labels: | ||
| attr: $3 | ||
| type: GAUGE | ||
| - pattern: "^org.apache<clsLdr=(.+), group=DataRegionMetrics, name=(.+)><>(Off[Hh]eap.*|MaxSize|PhysicalMemorySize|TotalAllocatedSize):" | ||
|
There was a problem hiding this comment. Are these the usual JVM memory metrics? There was a problem hiding this comment. Brian, no these metrics are collected through the whole cluster on specific |
||
| name: ignite_$1_$2_pages_bytes | ||
| help: Ignite durable memory pages size metrics in bytes | ||
| labels: | ||
| attr: $3 | ||
| type: GAUGE | ||
| # Apache Ignite provides a set of metrics for persistence when it's enabled for a specific data region. | ||
| # Note, PDS metrics is disabled by default. Use .enableMetrics() to enable persistence metrics collection on node. | ||
| # | ||
| # see https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/mxbean/DataStorageMetricsMXBean.html | ||
| - pattern: "^org.apache<clsLdr=(.+), group=\"Persistent Store\", name=(DataStorageMetrics)><>(Wal.*):" | ||
| name: ignite_$1_$2_pds_wal | ||
| help: Ignite WAL metrics | ||
| labels: | ||
| attr: $3 | ||
| - pattern: "^org.apache<clsLdr=(.+), group=\"Persistent Store\", name=(DataStorageMetrics)><>(LastCheckpoint.*):" | ||
| name: ignite_$1_$2_pds_checkpoint | ||
| help: Ignite persistence last checkpoint metrics | ||
| labels: | ||
| attr: $3 | ||
| type: GAUGE | ||
| # Apache Ignite allows to keep an eye on the distributed cache specific statistics available. | ||
| # Note, cache metrics is disbaled by default. Use .enableStatistics() to enable statistic collection for the cache. | ||
| # | ||
| # see https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/mxbean/CacheMetricsMXBean.html | ||
| - pattern: "^org.apache<clsLdr=(.+), group=(.+), name=.*(CacheClusterMetricsMXBeanImpl).><>(Rebalancing.*Rate):" | ||
| name: ignite_$1_$3_$2_rebalance_rate | ||
| help: Ignite cache $2 rebalancing rate | ||
| labels: | ||
| cache: $2 | ||
| attr: $4 | ||
| type: GAUGE | ||
| - pattern: "^org.apache<clsLdr=(.+), group=(.+), name=.*(CacheClusterMetricsMXBeanImpl).><>(RebalanceClearingPartitionsLeft|KeysToRebalanceLeft):" | ||
| name: ignite_$1_$3_$2_rebalance_left | ||
| help: Ignite cache $2 rebalancing data left | ||
| labels: | ||
| cache: $2 | ||
| attr: $4 | ||
| type: GAUGE | ||
| - pattern: "^org.apache<clsLdr=(.+), group=(.+), name=.*(CacheClusterMetricsMXBeanImpl).><>(Cache.*):" | ||
| name: ignite_$1_$3_$2_operations_total | ||
| help: Ignite cache $2 operations metrics | ||
| labels: | ||
| cache: $2 | ||
| attr: $4 | ||
| type: COUNTER | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
It'd be better to get the data from the individual processes directly, rather than adding jitter and lag.
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.
Brian, Could you, please, calrify? In general, I agree that it's better to share individual processes metrics. But I would like to have an batch of heap and non-heap metrics for the whole cluster.