Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Metric mq_cpu_ram_total_estimate_megabytes shows negative values #62

Closed
xbif opened this issue Mar 18, 2019 · 2 comments
Closed

Metric mq_cpu_ram_total_estimate_megabytes shows negative values #62

xbif opened this issue Mar 18, 2019 · 2 comments
Assignees
@echerniak
Labels
bug Something isn't working code Concerns code docs Concerns documentation
Milestone
Release 0.1.2.

Comments

@xbif
Copy link

xbif commented Mar 18, 2019

Both mq-exporter and IBM amqsrua could show negative value of "RAM total bytes".
On the picture you coould see, that at 7:00 a.m value was near 200, but at the 11:30 a.m it became minus 300
RAM total bytes

Command for amqsrua: ./amqsrua -m -c CPU -t QMgrSummary
@sberdyshev sberdyshev added bug Something isn't working docs Concerns documentation code Concerns code labels Mar 18, 2019
@sberdyshev sberdyshev added this to the Release 0.1.2. milestone Mar 18, 2019
@echerniak echerniak self-assigned this Mar 20, 2019
echerniak added a commit that referenced this issue Mar 20, 2019
@echerniak
issue62 readme updated with issue #62
2663352
@echerniak
Copy link
Contributor

This problem is related to this IBM
APAR. The problem appeared during testing the exporter on MQ ver. 9.0.1.0.
We could not reproduce this problem on MQ ver. 9.1.0.1 (this version
includes fix for APAR above). Unfortunately, there is no way to fix
this problem on the exporter side and the only option is to wait for
the fix from IBM for MQ ver. 9.0.x.x.

@echerniak echerniak mentioned this issue Mar 20, 2019
Merged
sberdyshev pushed a commit that referenced this issue Mar 20, 2019
@echerniak @sberdyshev
issue62 readme updated with issue #62 (#73)
542b095
@sberdyshev
Copy link
Contributor

Won't be fixed #73

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@echerniak echerniak

Labels
bug Something isn't working code Concerns code docs Concerns documentation
Projects
None yet
Milestone
Release 0.1.2.
Development

No branches or pull requests
3 participants
@echerniak @sberdyshev @xbif