We are not getting actual data on probes using usage_metering running from primary hub. 9.25 version is used and after creating ad-hoc scan the reports published missing some probe data.
We do not see all of the net_connect instances we were expecting.
Release : 20.x or later
Component : UIM - USAGE_METERING/BILLING
The report will not reflect net_connect until either an alarm is generated from that probe at some point or some qos data is received.
This is expected behavior.
If you would like to have the net_connect from that origin reflected immediately, you can turn on QOS temporarily (even just for a few minutes) for each of those net_connect probes.
Execute the "Run Scan Now" in usage_metering probe before running another report.
That will allow the net_connect to reflect in the report.