Stackdriver provides you with observability of all three layers. Stackdriver is GCP's fully managed native logging and monitoring tool. It gives you access to logs, metric, traces, and other signals from your infrastructure platform. Virtual machines, containers, middleware, and application tier, so that you can track issues all the way from your end users to your back-end services and infrastructure. Stackdriver aggregates, metrics, logs, and events from your infrastructure, giving developers and operators a rich set of observable signals, that speed root cause analysis and reduce mean time to resolution. Stackdriver doesn't require extensive integration or multiple pane of glass and it won't lock developers into using a particular cloud provider. Stackdriver dynamically configures monitoring after resources are deployed and has intelligent defaults that allow you to easily create charts for monitoring activities. Rich visualization and advanced alerting help you identify issues quickly, even harder to diagnose issues like, host contention, cloud provider throttling, and degraded hardware. This allows you to monitor your platform systems and application metrics by ingesting data such as metrics, events, and metadata. You can then generate insights from this data through rich visualizations and advanced alerting. A Workspace is a root entity that holds monitoring and configuration information in Stackdriver monitoring. Each Workspace can have between 1 to 100 monitored projects. You can have as many workspaces as you want, but GCP projects and AWS accounts can be monitored by more than one Workspace. A workspace contains custom dashboards, alerting policies, up time checks, notification channels, and group definitions that you can use with your monitoring projects. A workspace can access metrics data from it's monitored projects, but the metric data and log entries remain in the individual projects. The first monitor GCP project in a Workspace is called the hosting project and it must be specified when you create a Workspace. The name of that project becomes the name of your Workspace. To access an AWS account you must configure a project in GCP to hold the AWS connector. Because the Workspaces monitor all your GCP projects in a single place, a Workspace is a single pane of glass through which you can view resources for multiple GCP projects and AWS account. All Stackdriver users who have access to that workspace have access to all data by default. This means that Stackdriver role assigned to one person on one project, applies equally to all projects monitored by that Workspace. In order to give people different role for project and to control visibility to data, consider placing monitoring of these projects in separate Workspaces.
