NetFlow / IPFIX
Use detailed flow relationships for capacity, application and source-destination analysis.
ROUTING OPERATIONS
BGP Management
Manage GoBGP service health, peer sessions, announced networks and community policies centrally.
OPERATIONAL PURPOSE
Move from a network signal to verified context.
Connect routing state to live traffic and verified anomalies so changes are controlled, measurable and easier to review.
Investigation workflow
Begin with the global condition, narrow the scope by direction and subnet, identify the responsible source and destination relationship, and compare the result with historical behavior before taking action.
CORE CAPABILITIESACTIVE
- GoBGP service-health view
- Peer and session monitoring
- Network announcement management
- Community definitions and policies
- Routing actions linked to traffic evidence
SHARED DATA CONTEXT
Built to work with the complete Flowtrion platform.
This module uses the same inventory and telemetry model as realtime analytics, security controls, historical reporting and BGP operations.
sFlow
Maintain scalable traffic and PPS visibility across high-speed, high-port-count environments.
SPAN / Port Mirroring
Add focused packet-copy visibility for critical services, VLANs and investigation points.
OPERATIONAL WORKFLOW
Connect traffic evidence with controlled BGP operations
Routing action is safer when operators can see the traffic condition that triggered it. Flowtrion combines peer, route and community context with network telemetry to support reviewed operational decisions.
Data inputs and analysis
BGP session state, route information and configured community policies are evaluated alongside NetFlow, IPFIX or sFlow traffic signals. The exact control scope depends on the network design, router capabilities and the permissions assigned to Flowtrion.
Operators can validate an affected prefix, traffic direction, packet rate and destination distribution before considering a route or mitigation change. This creates a traceable separation between detection, approval and execution.
Operational outcomes
- Review peer and route context from one operational view.
- Validate traffic evidence before a BGP mitigation decision.
- Apply role and approval boundaries to sensitive actions.
- Maintain an auditable record of routing operations.
Deployment considerations
Use least-privilege credentials, explicit prefix and community allowlists, staged testing and rollback procedures. RTBH or FlowSpec workflows should be validated in a controlled environment before production use.
BGP context is especially valuable for DDoS, anomaly and capacity investigations where traffic and routing changes must be evaluated together.