As a service user:
- in order to use services managed by a 3rd party provider but still:
- monitor my app usage of the service. E.g.
- getting close to quotas/define service plans, and I need to update plans,
- suboptimal service usage by my app that requires optimization from app developers
- monitor performance of the service is within defined SLO
- I need to discover metrics exposed by the services I subscribed through my preferred platform,
- I need my app to access these metrics through the platform
As a service user, the metrics discovery is quite similar to service discovery in the catalog (along with discovery of service params, binding response, etc...). I.e. I can discover the list of metrics exposed to me, their format and a potential human description describing their semantics.
As a broker author, in order to provide metrics to service users and bound apps, I need a standard way of exposing metrics to platforms:
- a secured, authenticated way to provide metrics associated to each service instance and possibly service binding
- a portable way to provide metrics across platforms:
- available to both public services and private on-prem services (i.e. the service broker is'nt required to acquire privileged platform permissions to expose metrics to end-users)
Related pointers:
As a service user:
As a service user, the metrics discovery is quite similar to service discovery in the catalog (along with discovery of service params, binding response, etc...). I.e. I can discover the list of metrics exposed to me, their format and a potential human description describing their semantics.
As a broker author, in order to provide metrics to service users and bound apps, I need a standard way of exposing metrics to platforms:
Related pointers: