-
Notifications
You must be signed in to change notification settings - Fork 553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] Support Stackdriver Profiler #2116
Comments
Hi. Yes, this is on our radar. Stay tuned. |
Any news on this? We've recently rolled our continuous profiling for our Go services using Google Cloud Profiling, and would love to be able to do the same for our Ruby services. |
I was able to implement Cloud Profiler support separately: https://github.com/remind101/ruby-cloud-profiler This was just merged today, and hasn't been tested in production yet. Feedback would be highly appreciated! After some testing and refinement, it would be nice to get this incorporated into the Google libraries and officially supported. |
What's the status on this? I can see there's a client for Profiler but not much documentation on how to use it. |
The plan of record is to lean on OpenTelemetry profiling. There is a SIG working on it, and while the specification and SDK are probably still a ways off, we don't think it's prudent to create something bespoke that we'll just have to deprecate later in favor of OpenTelemetry. As noted above, there is a client for the Cloud Profiling service if you just need a way to upload profiling data. |
Currently Stackdriver Profiler only supports Go, Java, and Node.js, and it'll be nice if Ruby is also supported.
There were many cases where I had to ad-hoc debug OOMs and unintended high CPU usage, and Stackdriver Profiler can greatly increase application performance visibility alongside other Stackdriver tools like Trace. It can make debug much easier on the GCP console instead of debugging inside production machine manually.
The text was updated successfully, but these errors were encountered: