Releases: Vadims06/topolograph
v2.58 (08.03.2026)
Topolograph Release Notes v2.58
New Features
Traffic Engineering (TE) link attributes: Topolograph can now use TE data from your OSPF or IS-IS LSDB to show link-level traffic-engineering information on the diagram. You get visibility into link TE metric, administrative group (affinity), maximum and reservable bandwidth, and unreserved bandwidth per priority—useful for capacity planning, path analysis, and finding links that meet your TE constraints. When TE data is present, you can filter diagram links by TE metric or bandwidth from the UI and via the diagram edges API or the Topolograph SDK.

UI improvements:
- Graph background updated for better visibility
- Popup forms and compare form layout refined
- Edge tooltips: two-column layout and scroll for long attribute lists; bandwidth values formatted for readability
- Network Statistics text placement adjusted
- Network loading performance improved for large topologies
v2.55 (09.01.2026)
Bug fix
- API shortest path calculation for IS-IS using either Node hostname or SystemID
v2.54 (16.12.2025)
Improvements
- BGP-LS is onboarded, #70
- Fix applied for Monitoring logs visualization
BGP-LS demo https://youtu.be/gL0iqXgPJlE
v2.53 (29.09.2025)
Topolograph v2.53.0 Release Notes
#69 Done
New Features
Admin Panel for users

Admin Panel base page

🔐 API Token Management
- Long-lived API tokens with optional expiry field
- API authentication now supports both basic auth and Bearer tokens
- Token authentication for all API endpoints
📊 Graph Sharing System
- Share graphs between users via email
- Permission levels (read/write/admin)
- Optional expiry dates for shared access
- Secure access control - only authorized users can access shared graphs
- User Portal integration for easy management

v2.52 (24.09.2025)
Topolograph Release Notes v2.51
New Features
🔍 Enhanced Network Query Capabilities
Universal Node Identification
- New Parameter: Added
node_idparameter to/api/network/{graph_time}endpoint - Universal Support: Works with both OSPF (Router ID) and IS-IS (System ID/LSP ID) protocols
- Query Mode: Find all networks terminated by a specific node
- Usage:
GET /api/network/{graph_time}?node_id=10.10.10.1
Relative Time Filtering for Events
- New Parameter: Added
last_minutesparameter to event endpoints - Endpoints Affected:
/api/events/{graph_time}/networks/api/events/{graph_time}/adjacency
- Functionality: Get events from the last X minutes instead of absolute time ranges
- Usage:
GET /api/events/{graph_time}/networks?last_minutes=30
📊 New Monitoring API Endpoints
Graph Status Analysis
- New Endpoint:
GET /api/graph/{graph_time}/status- Analyzes network graph health
- Returns connection status and event summaries
- Includes host up/down events and cost change events
Enhanced Event Retrieval
-
New Endpoint:
GET /api/events/{graph_time}/networks- Network-specific event monitoring
- Returns network up/down events and cost changes
-
New Endpoint:
GET /api/events/{graph_time}/adjacency- Link-specific event monitoring
- Returns host up/down events and cost changes
🔧 Enhanced Graph Filtering
Advanced Query Filters
- New Parameters for
GET /api/graph:protocol: Filter by OSPF or IS-ISarea: Filter by specific areawatcher_name: Filter by watcher instancelatest_only: Return only the latest graph per watcher
- Usage:
GET /api/graph?protocol=OSPF&area=0.0.0.0&latest_only=true
API Schema Changes
Updated Response Formats
Network Endpoint Response
- Enhanced Description: Updated to reflect multiple query modes
- New Query Modes:
- Get all networks (no parameters)
- Get specific network by network/mask
- Find networks by IP address
- Find all networks terminated by a specific node
Event Response Schema
- New Fields:
single_host_up_events: Array of host up events as structured objectssingle_host_down_events: Array of host down events as structured objectsadjacency_cost_change_events: Array of link cost change eventsnetwork_cost_change_events: Array of network cost change events
Error Handling Improvements
- Enhanced Error Responses: Added 404 responses for "No graphs found" scenarios
- Better Error Messages: More descriptive error messages for API consumers
Backward Compatibility
✅ Fully Backward Compatible: All existing API calls continue to work without changes
✅ Optional Parameters: All new parameters are optional with sensible defaults
✅ Existing Endpoints: No breaking changes to existing endpoint behavior
Usage Examples
Find Networks by Node ID
# Find all networks terminated by OSPF Router ID
GET /api/network/2024-01-15T10:30:00Z?node_id=10.10.10.1
# Find all networks terminated by IS-IS System ID
GET /api/network/2024-01-15T10:30:00Z?node_id=0100.1001.0001Get Recent Events
# Get network events from last 30 minutes
GET /api/events/2024-01-15T10:30:00Z/networks?last_minutes=30
# Get adjacency events from last 60 minutes
GET /api/events/2024-01-15T10:30:00Z/adjacency?last_minutes=60Filter Graphs
# Get latest OSPF graphs only
GET /api/graph?protocol=OSPF&latest_only=true
# Get graphs from specific watcher
GET /api/graph?watcher_name=production-watcher&area=0.0.0.0Monitor Graph Status
# Check graph health and connectivity
GET /api/graph/2024-01-15T10:30:00Z/statusTechnical Improvements
- Performance Optimization: Improved network lookup using direct RID-to-network mapping
- Cost Change Integration: Path calculations now use updated link costs from watcher events
- Enhanced Monitoring: Better event tracking and status reporting
- Schema Validation: Improved API response validation and error handling
For detailed API documentation, please refer to the Swagger UI at /api/docs
v2.51 (31.08.2025)
Improvements
- IS-IS topology visualization on Monitoring page uses device names for nodes
install.shscript improved to install topolograph + OSPF Watcher or/and IS-IS Watcher with all dependencies for several minutes. Check demo video on Youtube https://youtu.be/imtVbqQYVWQ
Topology which has been built using OSPF Watcher
Fixes
- Monitoring page for IS-IS. When click on topology changes on the timeline dashboard -> highlight edge on the graph
- Huawei OSPF parsing fix ( received via https://t.me/topolograph/1 )
v2.50 (26.06.2025)
Bug fixes
- Mikrotik 7.18 OS OSPF visualization fix
v2.49.1 (14.06.2025)
v2.49
Monitoring page Improvements. From LSA to WEB Socket!
- Popup notification appears after each event
R3 <-> R2 adjacency down
R3 <-> R2 adjacency up
R3 <-> R2 adjacency cost change
Network down on R2
Network up on R2
Network cost change on R2
- Topology shows the most actual network state
Once OSPF Watcher detected that R3 lost adjacency with R2, new red popup events appeared. Click on spin button and topology marked it appropriately on the graph.
Details button shows extra metadata about the event.

Demo video on Youtube https://youtu.be/2IHbxmDVMA0 - Watcher includes local IP address in each logs

Please share your opinion about a message format and comment if you would like to enrich it with some more information.
v2.49.1
- Backend (and docker) version were updated from Python3.9 to Python3.11
- MongoDB updated from 4.0 to 6.0. In docker-compose file it's needed to change mongodb container version from 4.0 to 4.2, start docker compose (mongoDB does migration), then docker compose down, change mongodb container version from 4.2 to 4.4 or 6.0
v2.48 (10.05.2025)
Improvements
- Monitoring page. Previously network cost change was under
new/old Subnets

no it is underChange prefix

- Monitoring page. Hide all elements associated with the button that is unchecked when
Find logsandChoose the graphbutton pressed one more time - #32, New
Full sizebutton to resize graph area.

v2.47 (08.05.2025)
Improvements
- Bug fix #65: graph comparison and yaml-diagram upload issue





