-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
Not Selected
Feature Overview
...
Goals
We should emphasize ease of use for non-developer users and single pane through ACM UI.
The feature will enable users to define automated responses to specific conditions based on Search or Prometheus data, enhancing efficiency and reducing manual intervention, through a centralized, intuitive interface without requiring expertise in YAML or Ansible.
- As a system administrator/SRE, I need the ability to define automated actions that are triggered when specific scenarios are detected, such as alerts or predefined search criteria, so I can respond quickly and reduce operational overhead.
- As a system administrator/SRE, I need a centralized way to manage, monitor, and audit event-driven actions to ensure compliance, traceability, and alignment with organizational policies.
We should consider this could be valuable also in the single cluster use case and perhaps this UI integration can be done as an add-on that can be installed on single clusters as well as ACM.
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
| Requirement | Notes | isMvp? |
|---|---|---|
| Provide a simple UI for defining triggers and actions | The integration should allow users to define triggers and actions through a form-based interface, avoiding the need to write YAML or scripts. | Yes |
| Offer predefined templates for common scenarios | Include templates like "Restart VM on Alert" or "Update Labels on Search Results" to simplify the user experience. | Yes |
| Emphasize a single pane of glass for operations | Ensure users can configure and manage event-driven actions from the ACM UI without needing to switch tools or interfaces. | Yes |
| Include RBAC | Allow different levels of access (e.g., define vs. execute actions) to accommodate SREs and administrators, etc. | Yes |
| Hide underlying YAML/Ansible complexity | Abstract the technical details, ensuring users can perform operations without direct exposure to YAML or Ansible playbooks. | Yes |
| Allow custom playbooks behind the scenes | Enable advanced users or admins to upload or reference custom playbooks, while still abstracting this from non-technical users. | No |
| Provide a feedback and monitoring interface | Ensure users can monitor triggered actions (status, logs, and results) from the ACM UI itself. | Yes |
| Enable predefined Prometheus and Search integrations | Provide ready-to-use integrations with Prometheus alerts and Search queries to reduce setup time. | Yes |
| Support multi-cluster actions | Ensure actions can operate across multiple clusters managed by ACM while maintaining simplicity. | Yes |
(Optional) Use Cases
Examples:
- A user wants to restart a VM automatically when a high CPU usage alert fires.
- As an IT operator, unfamiliar with YAML or Ansible, needs to update labels for multiple non-compliant VMs identified by a Search query.
- A user wants to enable an action to snapshot a VM whenever a specific error alert fires.
Questions to answer
- ...
Out of Scope
- …
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
- relates to
-
-
- Backlog
-
-
CNV-51648 [cont] Plan Day2 Virtual Machines lifecycle management at scale support with ACM
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
