Google Cloud's operations suite (formerly Stackdriver) Reviews

I use the solution for logging, defining alerts, and monitoring. Our company's Java and Python logging teams mainly use it. 

As part of our company, we implemented several changes in our log analytics pattern, including the storage and procurement process. Earlier, before implementing the solution, our company was able to procure only one year of data, but later, we came to the three-year mark. Around 15-20% reduction has been witnessed in the total analytic consumption of our company.

The aforementioned result was possible because the solution allowed the creation of a dashboard where factors like storage costs, proportion of logs, and logs presence in a storage bucket or BigQuery can all be checked. Earlier all logs were stored in a raw storage, but currently our company is able to move logs in table bucket that contributes towards cost savings. 

It's basically for troubleshooting when you are in performance engineering load tests. Then all the logs are monitored from stack home, and each and every component that's involved is on there.

It has reduced the amount of time that we would take for troubleshooting.

We use the latest version of this solution for the storage of our logs. For example, we use Stackdriver to send our logs directly to GCP. We are able to pull metrics such as how many errors occurred, which service is giving the most amount of errors and which service is giving the least amount of errors. This solution is used by 50 people in our organisation. 

This solution could be improved if it offered the ability to analyze charts, such as a solution like Kibana.

We use it for a very basic purpose. Whenever we have some workload that is running, we turn on the hook to configure the monitoring.

It's easy to use. You don't have to do anything with it, just use it. Google provides an interface to get all the components monitored as long as you are plugged in. This is sometimes automatic.

I use Google Stackdriver for support monitoring.

I like the monitoring feature.

We use Stackdriver for real-time log management analysis, it provides cloud log in a fully managed service for the GKE requirements. We also use it to collect messages, some events,  metadata and the like from cloud. I'm the director and function head of risk and technology change, and we are customers of Google. 

The solution has improved our organization by reducing latency and also monitoring the costs of GCP usage by using the logging and monitoring features. We've been able to look at it and see the optimal size of infrastructure and figure out costing. That's a good site outcome, other than the regular application monitoring that we get.

Our use cases of Stackdriver are for cloud monitoring, cloud logging, and APM.

It has really been helpful in detecting, identifying, and troubleshooting issues with cloud services used in the organization.

While we are satisfied with the overall performance, in certain cases we must add additional metrics and additional tools like Grafana and Dynatrace. 

We would like to improve the application log. Most of these logs are derived from Grafana and not from Google Stackdriver. 

The application locker should be addressed. 

We have been using Google Stackdriver from the beginning, since 2019.