apps are made of services and apps might be part of a portfolio. For example, a bank may have online banking as a portfolio consisting of the following hierarchy:
mobile banking app -> consisting of account service and bill pay service
credit card app -> consisting of account service and payment service
In this example, SLO/SLIs defined at the service level would roll up to the corresponding app
Pre-requisite:
One or more SLOs have been defined for various services
Success Scenario:
Operations user (e.g. developer) picks which services should be grouped (ideally by consulting the service map)
System validates the following
the evaluation type is identical for chosen services (e.g periodic or aggregate but not mixing the two)
compliance period and type match
If the grouping are valid, SLI/SLO/error budget budgets are visualised
agaurav
commented
2 years ago 
apps are made of services and apps might be part of a portfolio. For example, a bank may have online banking as a portfolio consisting of the following hierarchy:
mobile banking app -> consisting of account service and bill pay service credit card app -> consisting of account service and payment service In this example, SLO/SLIs defined at the service level would roll up to the corresponding app
Pre-requisite:
One or more SLOs have been defined for various services Success Scenario:
Operations user (e.g. developer) picks which services should be grouped (ideally by consulting the service map) System validates the following the evaluation type is identical for chosen services (e.g periodic or aggregate but not mixing the two) compliance period and type match If the grouping are valid, SLI/SLO/error budget budgets are visualised