-map Edge Status stuck on "No Data" for all Network edges — interface speed + utilization present, edgeStatusConfig populated | Product Discussions

-map Edge Status stuck on "No Data" for all Network edges — interface speed + utilization present, edgeStatusConfig populated

Summary: David Bond is experiencing issues with edge status showing "No Data" on a saved topology map using MikroTik RouterOS switches monitored via SNMP. They are seeking clarification on the source and behavior of edge status data points, questioning the need for NetFlow data, differences in behavior for maps created via REST API versus UI, and the implications of an empty connections array. Patrick Rouse responds with detailed answers, directing David Bond to support documentation for further clarification on supported topology sources and data requirements for edge status.

I'm trying to get Edge Status (Max Utilization) to colour the connections on a saved topology map. Every Network edge shows No Data; hovering shows Status: ● No Data, and some edges show "No connection details found. Verify TopologySource and Datasource configurations."

I'm looking for what actually populates edge-status utilization.

Environment

Switches: MikroTik RouterOS, monitored via SNMP.
Topology from built-in Networking_L2_snmpSwitch (CDP/LLDP). Edges render fine.
Saved map created via the REST API (POST /topology/topologies, per-device views, Neighbours-1).

What's verified working

ERIs present on all switches (predef.externalResourceID).
SNMP_Network_Interfaces collecting on the switch ports: InInterfaceSpeed = 1000000000, InUtilizationPercent has values, auto.interface.speed set.
Connection Details on switch-to-switch edges show interfaces at both ends (e.g. Port16 [ID:16] ↔ bond0 [ID:7]), both up.
Map: showEdgeStatus = true; edgeStatusConfig populated (empty:false, networkConnection currentSelected: Utilization, thresholds low 50 / high 90).
(Also set ActualSpeed ILP on the parallel snmp64_If- instances — its ActualSpeed datapoint was No Data; now resolves — but edge status uses SNMP_Network_Interfaces, which never had a speed gap.)

Symptoms

All Network edges grey / No Data regardless of time range (tried Last 1 hour and Last 30 days).
GET of the saved map returns connections: [] (empty).
Interface + edge-config all only became complete within the last few hours.

Questions

What data source/datapoint actually drives Edge Status "Max Utilization", and over what window? Is there a backend compute cycle, and how long until it populates?
Does edge-status utilization require NetFlow (the ports have NetflowInUtilizationPercent but it reads 0), or is standard SNMP InUtilizationPercent sufficient?
Does a saved map created via the REST API behave differently for edge status than one built in the UI? Does it need Manual/Interface Mapping applied even when auto Connection Details already resolve the interfaces?
Is connections: [] on the saved-map object expected, or a sign the edges aren't wired for edge-status computation?

David Bond

Posted Jul 17, 2026 at 4:25 PM · Edited Jul 17, 2026 at 5:23 PM·Last reply 3 weeks ago

1 comment

Patrick Rouse

·3 weeks ago

Hi @David Bond . Below are answers to your questions. Please let us know if these do not resolve your issue.

1. What data source/datapoint actually drives Edge Status "Max Utilization", and over what window? Is there a backend compute cycle, and how long until it populates?

Answer -

During edge discovery, topology sources attach edge status data points to each discovered edge. For the list of supported topology sources and the required data sources for edge status, refer to the following support documentation: https://www.logicmonitor.com/support/saved-maps#h-edge-status

2. Does edge-status utilization require NetFlow (the ports have NetflowInUtilizationPercent but it reads 0), or is standard SNMP InUtilizationPercent sufficient?

Answer -

Edge status is driven by topology sources. For the list of supported topology sources and the required data sources for edge status, refer to the support documentation: https://www.logicmonitor.com/support/saved-maps#h-edge-status

3. Does a saved map created via the REST API behave differently for edge status than one built in the UI? Does it need Manual/Interface Mapping applied even when auto Connection Details already resolve the interfaces?

Answer -

Ideally, no. Edge status is driven by topology sources, and manual mapping edges are not eligible for edge status. Only edges that are automatically discovered by the supported topology sources participate in edge status. For more information, see the support documentation: https://www.logicmonitor.com/support/saved-maps#h-edge-status

4. Is connections: [] on the saved-map object expected, or a sign the edges aren't wired for edge-status computation?

Answer -

connections: [] represents the edge types configured for the saved map (for example, Network, Routing, Storage). Its presence or absence alone does not determine whether edges are wired for edge-status computation. Edge status depends on whether the edges are auto-discovered by supported topology sources and have the required edge status data available. Therefore, an empty connections array is not, by itself, evidence that edge-status computation is misconfigured; it should be evaluated along with the discovered edges, their types, and the availability of edge status metrics.

Please find attached a sample Saved Map API response with edge status computation details: