Feature Overview

We would need to limit the observability metrics that are exported to external receiver . 

Goals 

• limit the observability metrics that are exported to external receiver
• at same time we need to keep metrics what is collected for clusters
• align with a new MCOA stack in 2.15 the feature

Requirements 

 Use Cases

This Section:

•  customers who need to have limit what is exported to external endpoint.

Questions to answer

• How to migrate the old metrics stack  ? 

Out of Scope

• the metrics collector prior to ACM 2.15

Background, and strategic fit 

Assumptions

• ...

Customer Considerations

• To be usable the documentation must be top-notch contain an example and description of the feature . 

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)?
• This feature have a doc impact 
• *must be a new content in https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.15/html-single/observability/*
• Must be a New Content, with how to  limit the observability metrics that are exported to external receiver
•  documentation must be with full example of the  limit the observability metrics that are exported to external receiver . 
• What concepts do customers need to understand to be successful in
  [action]: the external receiver and a limit of metrics to external endpoint . 
• How do we expect customers will use the feature? For what purpose(s)?
• to  limit the observability metrics that are exported to external receiver
• 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)? New Content