You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched for a solution to the issue I'm experiencing after upgrading to the latest version of thold (1.8.2) and i think this is probably a bug.
When monitoring bandwidth utilization, thold is reporting an incorrect 'Current' value, which is often significantly higher than the actual utilization shown on the graph, leading to false alerts.
As an example, I have a 100G interface that is currently handling 32G of traffic, and I configured thold to trigger an alarm whenever the utilization exceeds 99% of the interface bandwidth, as determined by ifHighSpeed. However, in this case, thold is displaying the current value as 8.8 M. This functionality worked correctly in thold version 1.5.2.
Any help would be greatly appreciated
Attaching screenshot for reference:
The text was updated successfully, but these errors were encountered:
I have searched for a solution to the issue I'm experiencing after upgrading to the latest version of thold (1.8.2) and i think this is probably a bug.
When monitoring bandwidth utilization, thold is reporting an incorrect 'Current' value, which is often significantly higher than the actual utilization shown on the graph, leading to false alerts.
As an example, I have a 100G interface that is currently handling 32G of traffic, and I configured thold to trigger an alarm whenever the utilization exceeds 99% of the interface bandwidth, as determined by ifHighSpeed. However, in this case, thold is displaying the current value as 8.8 M. This functionality worked correctly in thold version 1.5.2.
Any help would be greatly appreciated
Attaching screenshot for reference:
The text was updated successfully, but these errors were encountered: