Network troubleshooting often means moving between device inventories, routing tables, interface data, and command-line queries to understand what went wrong. Engineers need to connect failed health checks with the affected devices, neighbouring systems, and recent changes before deciding what to investigate next.

Even with telemetry available in SuzieQ, finding the right query and interpreting results takes time and specialist knowledge. Stale data and incomplete checks can also make it difficult to distinguish a healthy network from one that simply lacks visibility.

This workflow connects SuzieQ to a shared network operations dashboard in Tines 3B. Hourly collection brings together device inventory and BGP, OSPF, interface, and EVPN health checks. Engineers can filter findings by namespace or hostname, review when issues were first observed, and explore changes recorded across collections.

From the same workspace, engineers can inspect device details, visualize network topology, and trace forwarding paths. Guided queries and a custom query builder make SuzieQ data easier to explore, while an OpenAI-powered assistant translates plain-language questions into read-only queries. It explains the results and shows the equivalent SuzieQ commands, helping engineers investigate failed BGP sessions, missing prefixes, and other connectivity issues.

The workflow reduces the manual effort involved in gathering network context and gives teams a clearer starting point for troubleshooting. Freshness warnings and explicit unavailable-data states help engineers assess the evidence before acting. All investigation remains read-only: the workflow does not change device configurations, and remediation stays with the engineering team.