[CES] Trigger Mode for event monitoring #2817
Assignees
Labels
Comments
Merged
5 tasks
otc-zuul bot
pushed a commit
that referenced
this issue
Feb 10, 2025
…mcloud_ces_alarmrule` (#2818) [Feat.] added possibility to trigger alarm immediately in `opentelekomcloud_ces_alarmrule` Summary of the Pull Request To trigger an event immediately, simply set the "period" parameter to 0 in your API request. Example API request to create an alarm rule with immediate triggering: URL: https://ces.eu-de.otc.t-systems.com/V1.0/bdcc63e2876b454bb0f625c9153d3a3e/alarms Body: { "alarm_name": "alarm-APIMON", "metric": { "namespace": "SYS.ECS", "metric_name": "deleteServer", "dimensions": [] }, "condition": { "comparison_operator": ">=", "count": 1, "filter": "average", "period": 0, "unit": "count", "value": 1 }, "alarm_enabled": true, "alarm_action_enabled": false, "alarm_level": 2, "alarm_type": "EVENT.SYS" } Related documentation: Creating an Alarm Rule Please note that this information is currently missing from the documentation but will be included in the next update. PR Checklist Refers to: #2817 Tests added/passed. Documentation updated. Schema updated. Release notes added. Acceptance Steps Performed === RUN TestCESAlarmRule_basic === PAUSE TestCESAlarmRule_basic === CONT TestCESAlarmRule_basic --- PASS: TestCESAlarmRule_basic (171.22s) === RUN TestCESAlarmRule_systemEvents === PAUSE TestCESAlarmRule_systemEvents === CONT TestCESAlarmRule_systemEvents --- PASS: TestCESAlarmRule_systemEvents (39.18s) === RUN TestAccCheckCESV1AlarmValidation --- PASS: TestAccCheckCESV1AlarmValidation (5.69s) === RUN TestCESAlarmRule_slashes === PAUSE TestCESAlarmRule_slashes === CONT TestCESAlarmRule_slashes --- PASS: TestCESAlarmRule_slashes (86.65s) PASS Process finished with exit code 0 Reviewed-by: Artem Lifshits Reviewed-by: Aloento Reviewed-by: Muneeb H. Jan <[email protected]>
|
thanks a lot for the fast reaction! |
|
Hi @sseifj, please check latest version v1.36.31 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I would like to clarify how to configure the trigger mode for event monitoring, specifically, setting it for immediate triggering versus the default accumulative mode. https://registry.terraform.io/providers/opentelekomcloud/opentelekomcloud/latest/docs/resources/ces_alarmrule#condition-1
As far as I understand, the current default behavior appears to be accumulative (evaluating over a 5-minute interval by default). However, I would like to configure the alarms to trigger immediately when the condition is met. I haven’t been able to find an explicit argument in the documentation that allows this configuration.
Could you please clarify:
-Is it possible to switch the trigger mode from accumulative to immediate?
-If so, what argument or configuration parameter should be used to achieve this behavior?
Any guidance or additional documentation on this topic would be greatly appreciated.
The text was updated successfully, but these errors were encountered: