Anomaly rules can be created from the Remediations screen of the Dashboard. Make sure you have selected the desired application using the Application Selector in the top-left corner of the dashboard.

From the Dashboard, select Remediations in the top navigation bar. Once on the Remediations page, select Add a Custom Rule.

Alternately, click here to be taken directly to the New Rule page.

Define the new rule

Begin by giving the new rule a name, description, and selecting the APIs it applies to.

Next, select which detection type to use.

  • Call by Call Filter Match: This type will analyze all API calls and attempt to match them against the filters set by the rule (you will define them shortly).
  • Sliding Time Window: This type allows you to set detection conditions such as Error Rate, Consumption, and Average Latency over a given time period. Once an API matches the set condition, the rule will begin analyzing API calls by any filters you apply.

Here, you can also decide whether to enable to disable this rule on creation. An enabled rule will begin watching for remediations immediately when saved.

Set up call filtering

Call filtering allows you to further narrow down the requirements for a remediation to trigger. Rules can have a max of 5 filters per rule, and can be set to match all or any of the filters.

Set the remediation type

For a remediation rule to function, it requires one remediation type to be selected. The available types are:

  • Block calls: Immediately block all calls that match the defined filters.
  • Timeout: Timeout all matched calls with the specified timeout delay.
  • Retry: Retry unsuccessful API calls that match the defined filters. The retry pattern, interval, and the number of retries can be set.

Set up notifications

With the filtering requirements and remediation type set, the last step is to set up notification settings. You can choose to be notified by email, Slack message, or webhook.

Once all the necessary fields are complete select Save to create your new Anomaly Rule.

Did this answer your question?