-
Feature Request
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
None
-
Future Sustainability
-
None
-
False
-
-
Telecommunications Program
-
None
-
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Enhanced Far Edge Monitoring Solution
2. What is the nature and description of the request?
For far edge deployments based on RH SNO config, it shall be possible to config the frequency of metrics transmission to every 30 secs. The implementation shall consider the following aspects,
- As the Far edge sites are compute resource constrained, the implementation should ensure to be within the allocated budget for CaaS to upto 2 Pcore.
- Standardized Alert Definitions: Define a set of standard alerts to capture crucial threshold breaches immediately.
- Local Alert Generation and Forwarding: Allow Prometheus to generate alerts locally in real-time, forwarding only critical alerts to the cluster manager.
- Support for Custom Alerts: Enable the addition of customizable alert rules to handle unique edge deployment scenarios, enhancing flexibility and responsiveness.
3. Why does the customer need this? (List the business requirements here)
At the far edge sites based on RH SNO, individual servers typically lack external alert management and user interface systems for real-time metric monitoring. Metrics collected are sent infrequently—every five minutes to ACM.
Challenges:
- Metrics sent at five-minute intervals may miss critical threshold breaches.
- Default metrics and alerts provided on the SNO are minimal, insufficient for real-time monitoring.
- Current approach could delay critical alerts, impacting operational reliability, especially in sensitive deployments like 5G network functions.
4. List any affected packages or components.
RHACM Multi Cluster Observability , Alert Manager
SNO Observability , Alert Manager