SLO-Gen AKS Archtiecture

[ppothepa24]

· We are planning to use the SLO-Generator as an API and deploy it on an AKS cluster( where SRE manages the SLO Generator Backend/ Platform which includes the Shared Configuration file).
· We have 700+ application "services" plan to adopt our SRE Slo Platform. Our plan is to pull the custom configuration that defines their SLOs from each of the 700+ Application/Services' repos and place it in a shared SRE SLO/Configurations repo. We have a CI/CD pipeline which will deploy the Custom Config YAML ( from Individual Services) onto the AKS Cluster. A cronjob that shall schedule the SLO-Gen run at regular intervals and push calculated SLO via HTTP POST Requests to the backend.

(1) What we wanted to understand was the "Exporter only" Mode of the SLO-Generator and understand what is the use case for teams to have access to the SLO-Gen directly and push an "SLO Report" into the SLO-Gen exporter mode? What specific use case does it solve and what are your thoughts on the above mentioned architecture?
(2) What are the limitations to our approach/ advantages of the "exporter only" approach?