Introduction

The Alerts report in the CacheFly Portal allows users to generate alerts based on configured thresholds for CacheFly services.

Some common and useful examples for the Alerts report are:

  • Alert if errors exceed the configured threshold

  • Alert if traffic drops below configured threshold

  • Alert if the cache hit ratio drops below threshold

Continue scrolling through this guide for more details on our Alerts report.

Where to Add and Edit Alerts

To add an alert:

  • Log in to the CacheFly portal

  • Navigate to the Advanced Analytics top-level menu and select Alerts

  • Click on +New alert to add a new alert

  • Follow the steps to create an alert

To edit an existing alert:

  • Click the dropdown arrow on the left of the alert

  • Click on Edit to bring up the alert configuration

Continue scrolling to view more details on configuring an alert.

Configuring an Alert

When configuring an alert, you will presented with the following conditions:

  • Type:

    • Delivery: Monitors delivery between end-users and CDN

    • Origin: Monitors requests between the origin and CDN

    • Cache: Monitors the Cache Hit Ratio (CHR) or Cache Byte Ratio (CBR)

  • Metric:

    • Requests: Will use the number of requests to match the Value condition

    • Traffic: Will use the amount of traffic to match the Value condition

  • Status Codes (Optional):

    • Available with the Delivery or Origin types

    • Allow alerts to monitor specific status codes (i.e. 200, 404, etc.) or wildcard status codes (i.e. 2XX, 4XX, etc.)

  • Comparison operator:

    • Equal to

    • Not Equal to

    • Greater Than

    • Less Than

    • Greater Than or Equal to

    • Less Than or Equal to

  • Value

    • The threshold value that you want to trigger an alert

      • The value for the Requests metric is number of hits

      • The value for the Traffic metric is the data amount for the selected Unit.

      • The value for the Cache alert type is the cache percentage for CHR or CBR

  • Unit (used with the Traffic metric)

    • The data unit to be used with the value threshold when setting a traffic alert

      • This unit measures the amount of data transferred for the selected service(s). The available units are Bytes, KB, MB, GB, TB, and PB

  • Interval

    • This is the internal at which the alert conditions are evaluated

      • For example, if an alert is configured for a 5 minute interval, we will monitor in 5 minute increments. After that monitoring period, if the alert conditions are met, an alert will be sent.

Once the conditions are configured, you will be able to give the alert a friendly name, select specific services or all services for the alert to monitor, and select the recipients that should be notified via email about the alert.

Pausing Alerts

There may be instances where an alert or alerts need to be paused for any number reasons.

To pause alerts, you can use the Deactivate option. This can be done by clicking the dropdown arrow to the right of the alert you wish to pause. Click the Deactivate button, then click the Deactivate button in the popup confirming the pausing of the alert.

Once the alert is ready to be reactivated, click the same dropdown and select Activate, then click the Activate button in the popup to begin monitoring again.

Removing an Alert

To delete an Alert, click the dropdown arrow to the right of the alert you wish to remove. Click the Delete button, then click the Delete button in the popup confirming the deletion of the alert.

Example Alert

Here, we have configured a simple alert to trigger after receiving 5 404s within a 5 minute period.

If you scroll to the second image, you will see an example email from a triggered alert. Clicking the affected service name(s) will take you to that services configuration.

Clicking View Stats will display the corresponding stats report during the time range of the alert.

Viewing Alert History

If more details for an alert are needed, you can use the History tab below Alerts on the left hand of the Alerts page. Here you will see a table with history of your alerts.

From here you can further drill down into the requests that triggered the alert. To view the logs, click View Logs to the right of the alert, which will redirect to our Logs report.

The Logs report will display a table with the requests that triggered the alert along with details for each request. The requests can be expanded using the dropdown button to the right of the log line.