Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to handle deployments crossing hundreds / thousands / more of "tenants" or "customers", each with API pricing, volumes, discounts, etc. that are potentially unique #16

Open
SSYH opened this issue May 24, 2021 · 0 comments

Comments

@SSYH
Copy link

SSYH commented May 24, 2021

We have many customers, and plan on using API Gateway (currently AWS) to do API forwarding as needed. For a given (functional) OpenAPI spec, we may have that 1:M relationship with SLAs; what is recommended best practice (or vision / backlog / roadmap) approach to managing such deployments? This would include per-tenant (per-customer) SLAs preferably integrated with monitoring / alerting / reporting tools which can then present in operations-facing and CSM-facing dashboards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant