Pyroscope and Grafana Phlare join together • Hacker News Board

Re: Pyroscope and Grafana Phlare join together

#21

Post by hairyhenderson » Wed, Mar 15, 2023, 6:56 PM UTC

IYasha wrote: post #19

I've heard "new" Grafana is running something like chromium for server-side rendering under the hood. Is it true? (it's freaking me out a bit) Sorry if it's a silly question.

What is "new" Grafana in this context? The only thing that sounds similar to this is the Grafana Image Renderer plugin, which uses Chromium. But that's hardly new (it's been around for about 4 years), and it's not part of core Grafana...

Re: Pyroscope and Grafana Phlare join together

#22

Post by Abekkus » Wed, Mar 15, 2023, 9:05 PM UTC

zokier wrote: post #15

I wonder if Grafana is going to rebrand at some point. They have been aggressively diversifying, but keeping the Grafana name makes people immediately associate the company with the Grafana product and consider the rest as side-projects.

As an engineer, I care about the other products of monitoring: tickets, alerts, reports. My management? The people with the money? All they think about from that stack is the graphs they can view on Grafana.

Re: Pyroscope and Grafana Phlare join together

#23

Post by anbotero » Fri, Mar 17, 2023, 4:30 PM UTC

felixge wrote: post #16

anbotero wrote: post #8

Earlier quoted context omitted.

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…

> we were just testing Datadog Continuous Profiling Felix from Datadog here :). We'd love to hear your thoughts on our profiler if you're willing to share them. My e-mail is in my profile. PS: Congrats to Ryan, Dmitry and team :).

Hey! It was alright, but at least for Ruby it didn’t report on the memory allocation of the calls, which is what we were looking for in the first place. We do not use it anywhere else, we only tried it for this pesky legacy system.