What’s New

Now you can use tags to classify alerts and find them more easily. The tags are optional and may be added to alerts when creating or editing them (and they work both for Platform Events and Runtime Alerts). After adding tags, you can use them as filters to look for alerts on the screens Runtime Alerts, Platform Events and Triggered Alerts.

The screen Triggered Alerts now indicates whether there was an error executing notification actions. Alerts with execution errors contain the icon in their cards, next to the button ACTIONS. And the field Action Status lets you filter for alerts with execution errors.

When you configure an alert of type Availability or of type Latency, you can now define a minimum number of calls that allows the alert to be triggered. See more about it here.

We standardised the times displayed on the screen Triggered Alerts so that they all reflect the user’s time zone. This applies both to the time when an alert was triggered (which already followed this pattern) and to the times displayed in notification messages (which were previously shown in UTC±00:00).

To be more precise in stating which API Platform objects are monitored, the labels "Certificate Info" and "Custom Interceptor" were changed to "Certificate" and "Custom Javascript Interceptor", respectively, with no modifications in how the alerts work. See the list of objects monitored here.

We added a new option of action for when an alert is triggered: Slack. Now it’s possible to send notifications to previously registered channels — and it works for both Platform Events and Runtime Alerts.

The Credentials screen is now called Integrations. In addition to the registration of authentication info to be used in webhooks, the screen now contains the SLACK tab, where you can integrate Flexible Actions to Slack workspaces. It’s from these integrated workspaces that the notification channels are selected.

The field to insert additional custom messages has moved to a different location. Before, it was part of the EVENT stage when creating an alert and now it’s under ACTIONS. With this change, it’s now possible to customise a message for each action registered — e-mail, Slack and/or Webhook. See more about creating alerts from API Platform events here and from monitoring APIs here.

When creating an alert to monitor HTTP response status, you can now include a code family (e.g., 5xx).

Regarding alerts from API Platform events, the label "AppToken" was changed to "App" (with no modifications in how the alerts work — the object app may be monitored regarding creation, update and deletion). See the list of objects monitored here.

To make notification times clearer, the cards on the Triggered Alerts screen now specify the time zone (GMT).

We added a new option of action for when an alert is triggered: Webhooks. With them, you can send an HTTP POST request to a previously registered endpoint — and it works for both Platform Events and Runtime Alerts. This option adds to email notifications, which were already present.