5 ms·
Shouldn't "long term snapshot for profiling and inverting call stacks" be table stakes by now?
by fbergen 2y ago
Shouldn't "long term snapshot for profiling and inverting call stacks" be table stakes by now?
- brancz 2y agoThe point of the first one is that you can create snapshots from within the product where profiling data isn't forever. This is so you can use the pprof.me link in a GitHub issue, PR, or elsewhere and trust that the data never goes away even if the original data went out of retention. We actually originally built pprof.me out of frustration that users of Prometheus (several of us are Prometheus maintainers) at best submitted screenshots of profiling data when all we wanted was an easy way to explore it. I agree that neither of these are terribly complicated features, but as far as I know no other product on the market actually has this combination. (yes, you can export data from most systems and use a different visualization tool but the point of products is to provide a single integrated package) (disclaimer: Founder of the company that offers the product featured in this case study.)
- fbergen 2y agoThanks for the reply I see, thanks for adding colour here I can see the benefits of a guaranteed immutable and permanent profiling data! Indeed even seemingly non complicated things do have a lot of devils in a lot of details :) Kudos of getting this out