- 16 Sep 2022
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Session Topology
- Updated on 16 Sep 2022
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Topology information can be added to a session to support correlation across all of the other reporting sessions to more expediently locate the source of performance degradations. It's purposely kept at an abstract level to support a provisioning model that isn't OSI layer specific = use what works for you, and that you can keep as up-to-date as possible.
Using Topology
Based on the provisioned topology and the metrics selected in the performance tab, Analytics will present a table of the aggregate performance across all of the sessions associated with each topology element, along with the number of sessions per element for reference as to the sample size. This is a great way to quickly identify an element that is mis-behaving and what its impacting.
Drill down using topology
Clicking on element will open up an analysis session where you can explore more about the element's performance and impact.
Modifying topology
This can be down via this UI or API.
Updating topology via UI
Updating topology via API
Topology is just like metadata and can be added via our monitored object operations like:
Note: Topology is uploaded as string with commas separating elements.
© 2024 Accedian Networks Inc. All rights reserved. Accedian®, Accedian Networks®, the Accedian logo™, Skylight™, Skylight Interceptor™ and per-packet intel™, are trademarks or registered trademarks of Accedian Networks Inc. To view a list of Accedian trademarks visit: http://accedian.com/legal/trademarks/.