Designing for observability with best practices
In this section, we will discuss some common observability architectures, how to build a cost-effective monitoring solution, and how to define an alerting and incident management strategy.
Choosing the right observability architecture
As mentioned previously, a Workspace can monitor up to 100 projects. It doesn't mean that you should always have a single Workspace for all your projects if you have less than 100 of them. Let's look into some of the common observability architectures and their pros and cons. However, before we get into these design patterns, it's useful to understand the three IAM roles related to monitoring:
- Monitoring Viewer: Gives the user read-only access to the Cloud Monitoring console and APIs
- Monitoring Editor: Gives the user read and write access to the Cloud Monitoring console and APIs, including writing monitoring data to a Workspace.
- Monitoring Admin: Gives the user full access...
