Thanks for your feedback!
EDIT
What has changed
Policies
In previous versions of Flexible Actions, alerts were based on each API.
To set up an alert for the same set of operations, but for multiple APIs, it was necessary to create multiple alerts, one by one, for each API.
The concept of policies changes this scenario. Now you can monitor multiple resources with just one registration.
| See how to set up a policy and establish the parameters that will trigger the alert and the APIs that will be part of this policy. |
Fixed or dynamic configurations (All or Any)
The All and Any options define whether the policy is fixed (the characteristics that trigger the alert are always the same you have configured/edited) or dynamic (the characteristics are automatically updated when the API is updated).
-
All: by selecting all API items (in Environment, Resource, and Operation) to be monitored by a policy, all these selected items at the time of policy creation or editing will be considered for triggering the alert. Items created after this definition will not be included in the monitoring.
-
Any: by selecting any API item (in Environment, Resource, and Operation) to be monitored by a policy, any item will be considered for monitoring, including additions and changes that occur after the policy definition.
Using the Any option provides greater dynamism to monitoring, as it will be automatically updated when new operations are created in the API.
On the other hand, the All option allows you to keep the monitoring parameters fixed as they were initially configured. New additions to the APIs must be manually configured to be included in the alert triggers.
| Click this link to see an example of how to use the Any option. |
Share your suggestions with us!
Click here and then [+ Submit idea]