Fix NETTX and NETRX negative values, polling time and accumulate values #162
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.
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.