[NMS-10352] Wrong data type for certain Cassandra JMX counters - The OpenNMS Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Resolved (View Workflow)
Priority: Minor
Resolution: Fixed
Affects Version/s: 22.0.3
Fix Version/s: Meridian-2018.1.2, 23.0.0
Component/s: Data Collection - JMX
Security Level: Default (Default Security Scheme)
Labels:

Description

MemtableSwitchCount from org.apache.cassandra.metrics.Keyspace and all the items under org.apache.cassandra.metrics.DroppedMessage are collected with GAUGE as the type.

According to the Cassandra documentation, their types are Counter and Meter, respectively, but cassandra30x.xml specifically fetches the Count attribute for the DroppedMessage items.

Due to this, all related values will continue to increase until Cassandra is restarted, which makes the graphs very difficult to read at a glance. Their type should be switched to counter correspondingly.

Dropped messages using gauge:

Dropped messages after switching to counter:

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

NMS-10352-counter.png
30 kB
13/Sep/18 6:57 PM
NMS-10352-gauge.png
21 kB
13/Sep/18 6:57 PM

Activity

People

Assignee:: Brynjar Eide

Reporter:: Brynjar Eide

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 13/Sep/18 3:52 PM

Updated:: 28/Sep/18 1:12 PM

Resolved:: 28/Sep/18 1:12 PM

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.