Recipes

xxxxxxxxxx

}'

egcurl --eg-section default --request POST \

  --url "https://$hostname/alerts/v2/alert-definitions" \

  --header "Accept: application/json" \

  --header "Content-Type: application/json" \

  --data '

{

    "origin": "STATIC",

    "fields": {

        "alertLowerBound": 5,

        "definitionId": "",

        "emailHtmlFormat": true,

        "isSum": true,

        "name": "myTestAlertName",

        "network": "myNetwork",

        "param": 20,

        "paramName": "cpercent",

        "templateId": "s@150",

        "email": [

            "nomail@akamai.com"

        ],

        "emailBrief": [

            "12345678@akamai.com"

        ],

        "group": [

            "grp_123456"

• Create a new alert

  Create a new alert definition based on a template.

  10 steps

  Open Recipe

• Get a template

  Fetch a specific template.

  5 steps

  Open Recipe

• Get an alert

  Get a single alert instance that is configured to fire under certain conditions.

  5 steps

  Open Recipe

• List alerts by fields

  List alert instances that are configured to fire under certain conditions.

  6 steps

  Open Recipe

• List alerts by definition

  List alerts and filter them by relevant fields or their values.

  5 steps

  Open Recipe

• Update an alert

  Modify the criteria that determines when an alert fires.

  6 steps

  Open Recipe

• Remove an alert

  Delete an alert and stop it from firing.

  5 steps

  Open Recipe

• Get alert details

  Get verbose details for a single alert, including its definition, firings, and sparklines report.

  5 steps

  Open Recipe

• List fired alerts

  List a history of an alert definition’s firings for the last 30 days.

  5 steps

  Open Recipe

• List modeling suppressions

  List all time ranges for an adaptive alert definition that are ignored when dynamically modeling its expected range of traffic.

  5 steps

  Open Recipe

• Unsuppress alert modeling

  Remove a suppression object. This makes an adaptive alert definition reconsider a previously suppressed period of time when modeling your site's expected range of behavior.

  6 steps

  Open Recipe

• List access control data

  This operation lists items of relevant data available to you at runtime to apply to an alert definition.

  6 steps

  Open Recipe

• Get an alert summary

  Get the summary of basic metadata for a single alert.

  5 steps

  Open Recipe

• List sparklines

  Get a set of sparklines, reports that plot anomalies that trigger firings over a time series.

  8 steps

  Open Recipe

• List active alerts

  List currently firing alerts for all alert definitions.

  3 steps

  Open Recipe

• Get adaptive alert edit history

  This API operation lists changes to adaptive alerts, allowing you to compare changes over time to an alert’s firings with the criteria that triggered them.

  4 steps

  Open Recipe

• Create a new modeling suppressions

  Specify a range of time for adaptive alerts to ignore when dynamically calculating a model of typically observed traffic and other behavior.

  6 steps

  Open Recipe

• Get definition schema

  Gets the JSON schema that describes the contents of a specific type of alert, depending on the template used to create it. This is useful to validate the contents of a new alert request before POSTing it.

  5 steps

  Open Recipe