Value Statement

We would like to solve the problem of sizing ACM observability for our users. They should not have to guess what resources to allocate for certain Thanos components that exist with ACM o11y, especially when they are facing scaling issues with it. Since our users lack domain knowledge, we would like to simplify this via t-shirt sizes, so that they can choose the size of components that fits them 

Definition of Done for Engineering Story Owner (Checklist)

• Users should be able to select a t-shirt size whilst installing/upgrading ACM o11y, to size their Thanos deployments
• They should be able to move between t-shirt sizes with a config change
• The t-shirt sizes should be mapped to certain measures of Thanos' ingest and query path such as head series, samples/blocks touched per query on average etc.
• It should still be overridable

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.