All of your Networks and Connections can be further managed by either adding, removing, or amending connections as well as the size of the network itself.
You can always add new Endpoints the same way as outlined in the Create your Network part. Simply click on Add End-points and select more endpoints. As you can see, the ones already belonging to a Network are disabled.
New endpoints will appear in the Network graph as independent items, however, would bring along their existing connections with endpoints that also belong to this network.
You can click on individual endpoints and granularly amend the connections they belong to. You can both add and remove those.
New connections would be displayed with a dashed line and removed ones would simply disappear to show you a new state of your network which would be done after applying changes.
To keep you always informed on the scope of changes we have a secondary confirmation step that outlines both newly added and deleted connections.
Deleted ones require a secondary step of confirmation.
Keep in mind that if the same endpoints are used in other networks, changes done here would reciprocally be reflected there, as well.
Network graph is fully adjustable and responsive to basic mouse actions - click & drag to move the network graph canvas.
To control the zoom level of Network Graph, you can use these actions:
- Touchpad pinch
- Double-finger touchpad movements
- Mouse wheel scroll
- Zoom In/Out buttons visible in the Graph
Network graph saves the coordinates of the endpoint position whenever you move it. This allows us to always provide you the network graph view as you left it the last time.
Network can not only be visualized in the Network Graph, or seen as a list of connections in the Connections table. You are also able to download a .yaml file outlining the current state of the given network.
Simply click the 'Download .yaml' button above the Network Graph to retrieve a file.
You can further use this file for Network configurations. More information about it can be found in YAML Configurations section
Network Graph isn't the only place where you can see and amend your Connections - there's also a table underneath it outlining all of the existing connections of the network you're currently looking into.
It looks very similar to the Endpoints table and contains key information about Connection such as the connected endpoints, their IDs, and the connection ID itself. It also contains information about the Status and the last update of the Connection.
There are five possible statuses that the Connection could have:
- Pending - this is the initial state which means that the connection is configured, however, we haven't received a handshake, nor any other signal that would indicate either a success or an error.
- Connected - that's self-explanatory, which means that the connection functions well, packet loss is below 1% and latency is below 1000ms.
- Warning - indicates performance issues that can either be related to packet loss or latency issues.
- Error - indicates serious errors either on the configuration level, or the agent side.
- Offline - indicates serious performance loss which allows us to claim that the connection is likely lost.
Agents are primarily used to configure connections, so after it's done - they can be removed and the connection would stay intact and active. Due to this, it is sufficient to have one active agent that would determine the connection's status.
Sometimes we might not be able to tell the exact current status as there might be periods of time, exceeding 5 minutes for which agents haven't exchanged any messages. We'll mark this as a sleeping connection, which you can see above.
For more information, always hover above the status and check the contents of a tooltip.
Connection statuses are also reflected in the network graph for every connection that has degraded or no connectivity.
As mentioned in the Endpoints section - every endpoint brings its Services and their setup to a Connection. However, this can also be managed on every specific Connection level in the very similar expandable bar as in Endpoints.
Endpoint services are disabled by default (unless specified otherwise in the Agent), so it's always a good idea to re-check specific Connections setup and enable services as needed.
In case of overlap or any connection errors, you will be presented with an error icon by the services facing those issues. After mitigating them (e.g. fixing a connection overlap) you can untick the service and tick again, so the re-configuration could happen.
Updated 15 days ago