If you were talking to someone whose organization is considering Google Stackdriver, what would you say?
How would you rate it and why? Any other tips or advice?
If you're moving to GCP, then Stackdriver is the right way to go. However, if you're moving to a different platform that's not GCP, Stackdriver may not integrate with it well. I would rate the solution higher but because we had some initial hiccups I would rate it an eight out of 10.
My advice to anybody who is implementing Google Stackdriver is to explore what metrics they want to use. I would rate this solution an eight out of ten.
Google Stackdriver is good because when you are using the GCP, there is no need to rely on any other monitoring tools, it gives the majority of the reports. But when you're stuck with any issue, and the team needs to do fine-tuning, it is a little difficult to analyze, especially while performing the load or stress tests. If everything is good, then you can get the reports. However, when something happens, they have to improve reporting. On a scale of one to ten, I can give Google Stackdriver an eight. As I said in our previous discussion, we are finding it difficult to develop the breakdown of the round-trip at a request level, especially pertaining to the response time. That's why if any drops happen in the network layer, it would be good if it could find out and then come up with some reasons, various reasons, potential reasons, why that drop happened and where the drop happened. Also, at the VPN level, there is a replay issue happening. Suppose the request is coming multiple times, we'll call it a replay issue. So to monitor the replay issue, if they would provide any specific functionality it would be good.
How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.