Live data from Hacker News

Pyroscope and Grafana Phlare join together

grafana.com

1–10 of 23 posts

Re: Pyroscope and Grafana Phlare join together

#2
This is great news.

At the company I work at, OpsVerse, we offer a single-click, packaged, pre-configured OSS-driven observability stack [1] that makes heavy use of Grafana (UI + Loki) as well as Pyroscope so it's great to see them take the route of merging projects rather than building a whole new project. Continuous application profiling is such a game-changer and as eBPF becomes more popular, I'm sure tools like pyroscope will become bread and butter for devs.

As an addon, we recently published a blog on how we ended us dogfooding pyroscope to debug a pesky memory leak [2].

---

[1]: https://opsverse.io/observenow-observability/

[2]: https://opsverse.io/2023/02/09/pyroscope-to-the-rescue-debug...

Re: Pyroscope and Grafana Phlare join together

#4
post #3

Hi! Tom from Grafana Labs here, super excited to welcome the Pyroscope team and can’t wait to see what they achieve. Continuous profiling is a next big thing IMO - easier to get started with than distributed tracing and delivers immediate value.

This is exciting news Tom! Looking forward to seeing some posts in the future on how using Pyroscope reduced spend by finding perf improvements.

Re: Pyroscope and Grafana Phlare join together

#5
post #2

This is great news. At the company I work at, OpsVerse, we offer a single-click, packaged, pre-configured OSS-driven observability stack [1] that makes heavy use of Grafana (UI + Loki) as well as Pyroscope so it's great to see them take the route of merging projects rather than building a whole new project. Continuous application profiling is such a game-changer and as eBPF becomes more popular, I'm sure tools like p…

Interesting!

What's the performance impact of continuous profiling in production for Node.js?

Re: Pyroscope and Grafana Phlare join together

#8
post #3

Hi! Tom from Grafana Labs here, super excited to welcome the Pyroscope team and can’t wait to see what they achieve. Continuous profiling is a next big thing IMO - easier to get started with than distributed tracing and delivers immediate value.

I’m really, really liking this.

I’ve been testing the whole stack on a local server, finding kinks, documenting workflows, because I hope I move us to this soon. Now with Pyroscope I would love to try it out even more. I kid you not, we were just testing Datadog Continuous Profiling for our legacy Ruby application not two days ago and it was quite lackluster.

Not saying this will be better (have yet to try), but I’d prefer to support and report feedback back on this for a brighter future for our community.

Keep it up!

Re: Pyroscope and Grafana Phlare join together

#9
post #8
post #3

Hi! Tom from Grafana Labs here, super excited to welcome the Pyroscope team and can’t wait to see what they achieve. Continuous profiling is a next big thing IMO - easier to get started with than distributed tracing and delivers immediate value.

I’m really, really liking this. I’ve been testing the whole stack on a local server, finding kinks, documenting workflows, because I hope I move us to this soon. Now with Pyroscope I would love to try it out even more. I kid you not, we were just testing Datadog Continuous Profiling for our legacy Ruby application not two days ago and it was quite lackluster. Not saying this will be better (have yet to try), but I’d…

Ryan here from Pyroscope -- Awesome to hear you're interested in migrating over. Would love for you to try out our Ruby integration and let us know what you think: https://pyroscope.io/docs/ruby/.

We've added a lot of features like tags/labels, integration with tracing: https://github.com/pyroscope-io/otel-profiling-ruby, integration with CI/CD (in rails), etc.

Feedback very welcome!

Post reply on HN