Create a Monitoring Session (Third Party Orchestration)
GigaVUE‑FM automatically collects inventory data on all target instances available in your cloud environment. You can design your Monitoring Session to include or exclude the instances that you want to monitor. You can also choose to monitor egress, ingress, or all traffic.
When a new target instance is added to your cloud environment, GigaVUE‑FM automatically detects and adds the instance to your Monitoring Session. Similarly, when an instance is removed, it updates the Monitoring Sessions.
For the connections without UCT-Vs, there are no targets that are automatically selected. You can use Customer Orchestrated Source in the Monitoring Session to accept a tunnel from anywhere.
You can create multiple Monitoring Sessions per Monitoring Domain.
To create a new Monitoring Session:
|
1.
|
Go to Traffic > Virtual > Orchestrated Flows and select your cloud platform. The Monitoring Session page appears. |
|
2.
|
Click New Monitoring Session to open the New Monitoring Session configuration page. |
|
3.
|
In the Alias field, enter a name for the Monitoring Session. |
|
4.
|
From the Monitoring Domain drop-down list, select the desired Monitoring Domain or click Create New to create a new Monitoring Domain. Refer to Create a Monitoring Domain section in the respective cloud guides.. |
|
5.
|
From the Connections drop-down list, select the required connections that are to be included as part of the Monitoring Domain. |
|
6.
|
Enable the Distribute Traffic option to identify duplicate packets across different GigaVUE V Series Nodes when traffic from various targets is routed to these instances for monitoring. |
Note: Distributed Deduplication is only supported on GigaVUE V Series Node version 6.5.00 and later.
|
7.
|
Click Save. The Monitoring Session Overview page appears. |