nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Service Interface Flow: Turning Live Interface Evidence into Directional Posture

i_like_eggs

Following on from my recent SolarWinds dashboard series, I have been experimenting with another way to represent live operational evidence.

This one is called Service Interface Flow:

The dashboard is rendered directly inside SolarWinds using SQL-generated HTML, CSS, and inline SVG over live Orion interface data.

Each scoped service interface is represented as a bidirectional evidence lane:

the left side represents inbound flow
the right side represents outbound flow
lane colour represents the resolved state for that direction
packet speed increases with directional utilisation
stale evidence remains visible as a dashed lane
hover cards expose the evidence behind the selected state
interface lanes can drill directly into the underlying trends view

The aim is not simply to animate traffic.

The aim is to make the operational story easier to recognise at a glance.

A heavily utilised outbound path should not falsely colour the inbound path red.

An interface with errors or discards should not look the same as a hard-down interface.

A stale polling signal should not quietly appear healthy.

The visual language is deliberately simple:

Green   → Healthy
Amber   → Warning pressure
Purple  → Degraded quality
Red     → Critical
Dashed  → Stale / Unknown

The moving packets are evidence as well:

Dot speed → directional utilisation

This is another small step in the same direction as the wider series:

Evidence → State → Problems / Advisory → Action

Previous dashboard series

Part 1: SolarWinds World Tour Dashboard - Pushing Dashboards Beyond the Default

Part 2: Observability Lens - A Glass View into the Evidence Layer

Part 3: Alert Pressure Skyline - Turning Alert Behaviour into Operational Posture

Part 4: Platform Observability Reactor - Monitoring the Monitoring

Part 5: Vector Engine - Resolving Live Evidence into Service Posture

Part 6: Closing the Loop - From Dashboards to Operational Storytelling

This one was too much fun not to share. ✌️

FYI, The screenshot uses normalised public labels, but the metrics and posture are driven by live Orion evidence

Find more posts tagged with

SolarWinds Self-Hosted Platform

custom dashboard

Observability solutions

npm - network performance monitor

Comments

vinay.by

@i_like_eggs - Another amazing post :) , Hats off to you my friend.

i_like_eggs

Thanks @vinay.by really appreciate it my friend. 😎

I thought the series was finished, but this one was too much fun not to share

i_like_eggs

I have just realised I have been scrolling up and down the interface list watching the different lanes light up 😂

I swear it was not more than ten minutes 🫣, but it is ridiculously satisfying watching the directional posture move across the interfaces in real time

silverbacksays

Ok. SWI need to just straight employ @i_like_eggs to work on the OSH GUI.

Well played! I would love to see how I could get any of this to work on lab, let alone my client instances.

naveensingh43

Once again, an amazing post—well done!

Quick Links

Alert HTML Content
Alert Cleared.htmlHello, I would like to share the HTML template details we have prepared so that Solarwinds alarms can become more meaningful. It can list alarm object details and connected device details separately in HTML template. Except for object and device details, you can easily add custom property information…
Cisco ASR Devices
Cisco ASR Devices.pollerCisco ASR Devices
Basic SWQL Syntax
SWQL is built on the framework of SQL and as such supports most of the standard clauses as part of a query. A very simple example query is: SELECT Caption, IPAddress, Vendor, ResponseTime FROM Orion.Nodes Dissecting this query is relatively straightforward: show some fields (Caption, IP address, Vendor, and Response Time)…
Cisco ASA SSL Tunnels
Active SSL Tunnels-ASA.UnDPThis poller *should* display the number of Active SSL VPN (Anyconnect) Tunnels currently connected to your box. However, I tried it with my 5520 running 8.0.4 and for some reason I get a OID Not Supported. Here's my post in the forum: *EDIT* This is confirmed working with at least Interm release…