Overview
Last updated
Was this helpful?
Last updated
Was this helpful?
The Overview menu section is designed to provide you with both real-time and historical data about your application through informative graphs.
These graphs are intended to give you insights into your application's performance and health, allowing you to oversee and enhance its reliability and performance. The presented metrics display application status data and provide valuable information about the errors that have occurred.
First of all, we’ll consider the in the upper part of the panel and then proceed with the .
Using the top management panel, you are able to:
In the upper frame section, you can see the drop-down list, showing your project’s domain name by default.
Upon clicking on it, you’ll be shown the list of your service’s ADNs and CDNs. When switching between them, the information on the graphs within this section will be changed appropriately.
By opting for the Live drop-down option in the upper frame part, you are able to switch between real-time and historical data.
Here, you can choose both start and end dates from the displayed calendar to view data within your selected date range.
Alternatively, you can select a predefined time frame within the list of provided ones:
Live (i.e., the real-time mode)
Today
Yesterday
This Week
Last Week
This Month
Last Month
Last Three Month
Last Six Month
When you choose any of the above-listed options, the data on the graphs below will change accordingly.
Herewith, the level of data granularity is determined by the selected time frame - the shorter period is chosen, the smaller are the intervals between data points on the graph. For instance, if you opt for a 1-day range, the graph displays data points every 5 minutes. For a one-week range, the interval increases to 15 minutes, and so forth. This allows you to examine data with varying levels of detail based on your preferences.
The Purge option to the rightmost is designed for the immediate removal of cached content on delivery endpoints (i.e., ADN(s) and CDN(s)), compelling the system to fetch the updated data from the origin. This function comes in handy in case you've made changes to your application and want them to be immediately visible to your users, or when newly updated content hasn't been replicated correctly.
By clicking on it, you’ll be prompted to choose one of the options - either Purge URL or Purge All.
Depending on your selection, the flow will be the following:
Purge URL
You’ll be faced with a pop-up window where you need to point to the required page address within the chosen delivery endpoint domain.
E.g., if you’d like to clear the cache for the edgeport.info/blog page, you need to type the ‘blog’ entry within the provided field and click Purge to execute this process:
And if you specify the asterisk '*' symbol here, the system will clear cached data for all directories within that domain.
Purge All
When selecting this option, all cached assets on all endpoints (i.e. both ADNs and CDNs) will be removed.
Please be aware that after clicking this line, the purging will be initiated immediately.
Now, let’s consider in more detail the graphs this dashboard section provides:
Through the first chart, you can monitor the global traffic. In the Live mode, the interactive map displays the traffic's geographical origins through circles that appear on the corresponding map locations. Each circle’s size is determined by the amount of current incoming traffic in bits per second (i.e. bandwidth), while hovering over any of it reveals the appropriate Point of Presence (PoP) location and the exact connection bandwidth value.
The next chart illustrates the total outbound bandwidth being utilized by your application (bits per second transfer).
This metric assists you in evaluating your network's performance and ensuring that the throughput is sufficient for your business requirements.
This chart is intended for tracking the HTTP status code responses. These responses can come from the Edge when requests access the cache, or from your service’s origin if the request is bypassed to the backend.
By understanding and analyzing these codes, you can gain deeper insights into the application's behavior, identify potential bottlenecks or issues, and optimize its performance.
The value on the vertical axis represents the average number of HTTP responses with a particular code received per second, based on data from the last minute.
The responses' code numbering is standard and should be understood as follows:
2xx successful – the request was successfully received, understood, and accepted
3xx redirection – the request hit the cache layer or some further action such as redirection has taken place
4xx client error – the request contains bad syntax or cannot be fulfilled
5xx server error – the server failed to fulfill an apparently valid request
Within this chart, you can gain valuable insights into the cache requests' distribution, showing those utilizing Edge caching (Hit), and those that have been routed to the backend for data retrieval due to the following reasons:
Uncacheable - the requested data asset's Cache-Control and Expires headers indicate that it should not be cached on a PoP or by the HTTP client.
Additionally, the None line represents the requests for which it’s unclear whether they end up at a cache layer or were directed to the service’s origin, and the Total one expectedly reflects the overall cache requests’ processing.
The value on the vertical axis shows the average number of cache request statuses received per second, based on data from the last minute.
This chart is designed to monitor the currently active connections between end-users and the Edge.
Please pay attention that the connections displayed here refer specifically to open TCP links and do not indicate the number of users currently connected to the website.
The value on the vertical axis shows the average number of new connections per second based on data from the last minute.
Towards the bottom of the page, you'll find a list of recorded events. Here, an event is defined as any action taken by a user with access to managing your service in terms of changing service configuration.
This way, if you've shared access to your service with collaborators, you can track all the actions that other users take alongside you.
If switching to the , the traffic distribution will be displayed according to country borders. Hovering over a specific country will display its name and the total amount of traffic received from that location within the specified date range.
The Frequency period in the upper pane designates the time frame for which the data is currently shown on a graph. Kindly be aware that changing it will reset the collection of monitoring data for all three , , and graphs.
The Frequency period in the upper pane designates the time frame for which the data is currently shown on a graph. Kindly be aware that changing it will reset the collection of monitoring data for all three , , and graphs.
For more detailed information on each code description, please refer to the .
Config No Cache - the requested data was defined as such that should not be cached according to the Edgeport settings
The Frequency period in the upper pane designates the time frame for which the data is currently shown on a graph. Kindly be aware that changing it will reset the collection of monitoring data for all three , , and graphs.
This data is displayed for tracking purposes in the Live only.
To invite your colleagues to join you in managing your service within the Edgeport platform, refer to the dashboard section.
