BugZero updated this defect 56 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
3/24/2024
SD-WAN by VeloCloud
No affected releases provided.
No fixed releases provided.
On a VMware SD-WAN Orchestrator using either Release 3.3.x or 3.4.x, when a user goes to Monitor->Edge pages for a VMware SD-WAN Edge with high traffic throughput, the user may observe statistics to be missing if selecting a sufficiently large time range.
Beginning with VMware SD-WAN software release 3.3.0, a database query limit was introduced and set to one million matches. For high traffic Edges, if there are more than one million data points to display for a particular time range, the result will be incomplete displays in the Monitoring section of the Orchestrator. In Monitoring, graphs will be incomplete as a result of not fully populating all available data. This is an expected behaviour.This issue will be addressed in Release 4.0.0 with the expectation that an Orchestrator using Release 4.0.0 would correctly display all data points Monitoring statistics regardless of the number of data points returned for a particular time range.
This is a display issue and has no impact on customer traffic for a given Edge. All Edge statistical information is fully present in the Orchestrator database, the data is just not shown fully on the Orchestrator's GUI when querying a time range that returns more than 1 million data points.
To see the full data set reflected in the graph, reduce the time range to a narrower window.There are also alternative solutions to monitoring events and statistics, such as SNMP, Netflow, and Syslog.Please refer to the VMware SD-WAN by VeloCloud Administration Guide for more details on configuring one of the above monitoring solutions.
For partners managing an on-premise Orchestrator, you may reach out to VMware SD-WAN Technical Support for additional configuration options.