Assisting with the support of solutions in operation
In this tutorial we will learn and understand about assisting with the support of solutions in operation.
Google Cloud’s operation suite monitor, troubleshoot, and improve application performance on your Google Cloud environment. Further, it also:
- Firstly, collect metrics, logs, and traces across Google Cloud and your applications
- Secondly, use built-in out-of-the-box dashboards and views to monitor the platform and applications
- Thirdly, query and analyze these signals
- Then, set up appropriate performance and availability indicators
- Lastly, set up alerts and notification rules with your existing systems
Google Cloud’s operation: Key features
- Firstly, Real-time log management and analysis. Cloud Logging is a fully managed service that performs at scale and can ingest application and system log data. Further, it also includes custom log data from GKE environments, VMs, and Google Cloud services. Cloud Logging allows you to analyze selected logs and accelerate application troubleshooting.
- Secondly, Built-in metrics observability at scale. Cloud Monitoring provides visibility into the performance, uptime, and overall health of cloud-powered applications. Collect metrics, events, and metadata from Google Cloud services, hosted uptime probes, application instrumentation, and a variety of common application components.
- Thirdly, Monitor, and improve your app’s performance. Application Performance Management (APM) combines monitoring and troubleshooting capabilities of Cloud Logging and Cloud Monitoring with Cloud Trace, Cloud Debugger, and Cloud Profiler, to help you reduce latency and cost, so you can run more efficient applications.
Cloud Monitoring
Cloud Monitoring measures key aspects of your services, gives you the ability to graph the measurements and notifies you when the measurements don’t have acceptable values.
Monitoring techniques
Cloud Monitoring provides you with four kinds of monitoring:
- Firstly, Black-box monitoring enables you to probe your service by requesting a web page, connecting to a TCP port, or making a REST API call. This type of monitoring provides no information about the internals of your service.
- Secondly, White-box monitoring enables you to monitor aspects of your service that are important to you. However, you can instrument your service to write time-stamped data by using a library like OpenCensus. Further, you can write custom time-series data by using the Cloud Monitoring API. For more information, see Using custom metrics.
- Thirdly, Grey-box monitoring collects information about the state of the environment in which your services are running. This type of monitoring is provided by a combination of Google Cloud products and third-party partners of Cloud Monitoring, such as Blue Medora.
- Lastly, Logs-based metrics are metrics collected from the content of logs written to Cloud Logging. The predefined logs-based metrics include, for example, errors that your service detects or the total number of log entries received. You can also define custom logs-based metrics.
Reference: Google Documentation, Doc 2