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.

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

Fix NETTX and NETRX negative values, polling time and accumulate values #162

Merged
merged 1 commit into from
Dec 2, 2016

Conversation

n40lab
Copy link
Contributor

@n40lab n40lab commented Nov 23, 2016

Negative values are not processed. Negative values mean that PerfomanceManager doesn't consider them valid.

A LAST_MON element is used in the MONITORING section to track when was the last time the information was requested so it helps to calculate how many 20 seconds samples are queried to the PerformanceManager.

The following metrics are used: 'net.transmitted','net.bytesRx','net.bytesTx','net.received'. Max value between net.transmitted and net.bytesTx is used as the transmitted bytes (same for reception).

Current NETTX and NETRX are sumed to last monitored values so they are accumulated.

@tinova tinova merged commit dbb3f8e into OpenNebula:one-5.2 Dec 2, 2016
rsmontero pushed a commit that referenced this pull request Aug 26, 2020
rsmontero pushed a commit that referenced this pull request Oct 6, 2020
Signed-off-by: Jorge Lobo <[email protected]>
(cherry picked from commit cf68d2f)
rsmontero pushed a commit that referenced this pull request Jan 20, 2021
rsmontero pushed a commit that referenced this pull request Apr 13, 2021
Signed-off-by: Jorge Lobo <[email protected]>
(cherry picked from commit cf68d2f)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants