1. Proposed title of this feature request

Adding support for configuring the logging collector to receive firing alerts from Alertmanager Pods as an HTTP server

2. What is the nature and description of the request?

Currently, it is only supported to configure the collector to receive audit logs as an HTTP server, as noted here:

https://docs.redhat.com/en/documentation/red_hat_openshift_logging/6.4/html/configuring_logging/cluster-logging-collector#configuring-the-collector-to-receive-audit-logs-as-an-http-server_cluster-logging-collector

It would be beneficial if it were also supported to configure the collector to receive firing alerts from Alertmanager pods.

3. Why does the customer need this? (List the business requirements here)

Convenience: Since both Vector and AlertManager are features provided by Red Hat, OCP cluster alerts can be received using only the functionality included in the OpenShift subscription. Given that an external server executing the oc client is typically already available, this eliminates the need to prepare or utilize external services (such as Slack or SMTP) as notification destinations for AlertManager.

Reliability (Operability): When relying on a single external service (such as Slack or SMTP), there is a potential risk that alert notifications may fail (or detection may be delayed) if that external service experiences an outage. If this scenario is supported, an alternative monitoring route can be secured in addition to the single external service, allowing for rapid response and preventing missed detections.

Cost Reduction: Eliminating the need to prepare or use third-party services (such as Slack or SMTP) for AlertManager notifications is expected to reduce both service usage fees and operational costs.

4. List any affected packages or components.

OpenShift Logging - collector (Vector)

OpenShift Monitoring - Alertmanager