Release Notes 2021

Release Notes 2021

May 2021

You can now use tags to classify alerts and find them more easily. Tags are optional and can be added to alerts during creation or editing (they work for both Platform Events and API monitoring notifications). Later, tags can be used as filters to search for configured alerts on the Runtime Alerts and Platform Events screens, or triggered alerts on the Triggered Alerts screen.
The Triggered Alerts screen now displays errors when notification actions configured for an alert fail to execute.
Alerts with failed actions show the icon next to the ACTIONS button on their card. You can also filter alerts with failed actions using the Action Status field in the search area.
When configuring an Availability or HTTP Response Status alert, you can now set a minimum number of requests required for the alert to be triggered. Learn more about this here.
We standardized the times shown on the Triggered Alerts screen to reflect the user's timezone. This applies both to the alert trigger time (which already followed this pattern) and to the times displayed in notification messages (previously shown in UTC±00:00).
To clarify monitored objects in alerts from API Platform events, the labels "Certificate Info" and "Custom Interceptor" were changed to "Certificate" and "Custom Javascript Interceptor", respectively, with no changes to alert functionality. See the list of monitorable objects here.

Added a new action option when an alert is triggered: Slack. You can now send notifications to a previously registered Slack channel — this works for both Platform Events and Runtime Alerts.
The Credentials screen is now called Integrations. In addition to registering authentication information for use in webhooks, the screen now includes a SLACK tab, where you can integrate Flexible Actions with Slack workspaces. Notification channels are selected from the integrated workspaces.
The field for adding additional custom messages has moved. Previously, it was part of the EVENT stage when creating an alert; now it is within the ACTIONS step. With this change, you can customize a message for each registered action type — email, Slack, and/or Webhook. Learn more about creating alerts from API Platform events here and from API monitoring here.
When creating an alert to monitor HTTP response codes, you can now include a code family (e.g., 5xx).
For alerts from API Platform events, the label "AppToken" was changed to "App" (no changes to alert functionality — the app object can be monitored for creation, editing, or deletion). See the list of monitorable objects here.
To clarify notification trigger times, cards on the Triggered Alerts screen now specify the timezone (GMT).

Added a new action option when an alert is triggered: Webhooks. You can now send an HTTP POST request to a previously registered endpoint — this works for both Platform Events and Runtime Alerts. This option is in addition to email notifications, which already existed.
- To assist with webhook registration, a new page was added to the main Flexible Actions menu: Credentials. Here, you can register authentication information (client ID/secret) to be included in notification requests.