A customer may require more resources in within the openshift monitoring stack in order to use the CMA prometheus scaler, which is able to use the thanos querier, to retrieve prometheus metrics from the cluster. Heavy usage of the scaler may require more resources/higher rates for higher throughput, but we don't know how much scaling is needed or even what needs to be scaled.

Similar to https://issues.redhat.com/browse/PODAUTO-94, we'd probably like to know something like "we suggest X resources per Y of something" and/or the "Thanos Querier requires X resources per prometheus scaler/trigger", or "requires X amount of pods in HA per prometheus scaler/trigger".

Acceptance Criteria:

• A document exists that contains these resource/rate requirements for CMA or thanos querier
• A Jira ticket exists that tracks the needed documentation change

Slack conversation that led to this: https://redhat-internal.slack.com/archives/C02F1J9UJJD/p1738266446014769