WHAT

Replace the source metrics or work out a migration plan for the metrics which are exposed as part of the RHOSAK public API.

WHY

Kafka Fleet Manager, KFM, gets its metrics from Observatorium, but it's picking a specific set of metrics from there (and a specific set of labels for each of those). All metrics exposed through the KFM API (for use by the console UI, or available to customers through the any of the endpoints like the Prometheus-scrapable endpoint) will need to be accounted for. You can see all of the metric names (and labels) that are exposed here: https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/blob/8711a4ba73e99d78813a5b81878e5c2bff0521b5/internal/kafka/constants/metrics.go#L48

HOW

• What metrics are currently part of the public API and what do they mean?
• What are the replacement metrics from the new quota plug-in?
• How do we maintain both sets?

DONE

Include the following where applicable:

• <bulleted list of functional acceptance criteria that need to be completed>
• <call out anything on the documentation side that's needed as a result of this task being completed>
• <any metrics, monitoring dashboards and alerts that need to be created or be updated>
• <SOP creation or updates>

Guidelines

The following steps should be adhered to:

• Required tests should be put in place - unit, integration, manual test cases (if necessary)
• CI and all relevant tests passing
• Changes have been verified by one additional reviewer against:
• each required environment
• each supported upgrade path
• If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged