All Collections
Service
Dashboard
The structure of the dashboard
The structure of the dashboard
Updated over a week ago

This tutorial explains the structure of the dashboard. The dashboard provides information in a real-time and historical mode for the following:

You can leverage the data and the information for better insights and monitoring purposes as well as to improve the application's performance and reliability, as the metrics are application-aware and can provide you with helpful information for errors.

Global Traffic

In the first chart, you can monitor the global traffic. The map provides an interactive mode in real-time, so you can analyze where the requests are coming from (Client Country) and from which edge points are being distributed (PoP).

Bandwidth

In the second chart, you can monitor the outgoing bandwidth that the application is utilizing not only in real time but also in historical mode. Please note that on Edgeport, we only measure the outgoing traffic from the edge to the end-user and not from your origin to the edge.

HTTP Status

In the third chart, you can monitor the HTTP status code responses in real-time or historical mode. These responses come from the Edge when they hit the cache, or your origin when the request is bypassed to the backend.

Cache Status

In the fourth chart, you can monitor the Cache Status codes responses in real-time or historical mode. These responses are all related to the Edge, and it determines when a request has been delivered from the Edge or your origin.

Connections

In the fifth chart, you can monitor the open connections that end-users have with the edge. Please note that connections are TCP open connections only, and they do not determine the website's users.

Events

At the bottom, you can monitor the Events. The events are actions that users have created for the service, acting like activity logs. Please note that if you have shared a service with a collaborator, you will be able to monitor any actions that this user is proceeding with on the service.

Did this answer your question?