Systems/Inet Uplink-01/

Network

INET-UPLINK-01

HealthyConfigured
Generic ISPWAN EdgeNetwork Device7 sec ago
Topology
Defined Signals9
Simulated6
Not Collected3
Recent Events1
Upstream Systems1
Downstream Systems1
Simulated values are not live telemetry. Not collected signals require SEYDRA Edge, an agent, SNMP, syslog, an API, or a vendor integration before SEYDRA can report customer data.
Visible
Host
0 groups · 0 not collected
Visible
Application
0 groups · 0 not collected
Visible
Media
0 groups · 0 not collected
Needs collector
Network
2 groups · 3 not collected
Visible
Storage
0 groups · 0 not collected

Monitoring Details

Host, application, media, network, and storage context separated so engineers can see where a problem lives.

1 monitored groups
Network Layer

Ports, packet loss, timing path, WAN state

2 groups
Internet / WAN Edge

Transit health between on-premises encoding and cloud distribution.

Simulated
Transit
Simulated
Primary
Utilization
Simulated
41%
Packet loss
Simulated
0.03%
Latency to cloud
Simulated
21 ms
BGP session
Simulated
Established
Firewall policy
Simulated
SRT egress allowed
Required WAN Collectors

Live circuit, routing, and firewall state require router APIs, firewall logs, syslog, or provider monitoring data.

Not collected
Firewall session logs
Not collected
Collector not configured
BGP neighbor monitoring data
Not collected
Collector not configured
ISP circuit alarms
Not collected
Collector not configured

System Information

What kind of machine or service this system runs on, and how SEYDRA knows.

Configured
System PlatformNetwork Device
Information SourceInventory record
Form factorWAN edge / firewall / router
Real model, OS version, BGP state, and firewall sessions require network monitoring data collection.

Recent Events

Grouped by where the signal came from, so host problems and application problems do not blur together.
Network
Network
info
Primary internet transit path carrying SRT egress to cloud distribution.
09:45:55 · INET-UPLINK-01

Related Incidents

No related incidents.

Not Collected

These signals remain unavailable until a compatible collector is configured and reporting.

Required WAN Collectors
Not collected
Firewall session logsCollector not configured
BGP neighbor monitoring dataCollector not configured
ISP circuit alarmsCollector not configured