You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pyroscope ecosystem is around Go pprof. I think it makes sense that the agent would be able to emit pprof natively in order to improve data flows that would operate on the canonical form. It can make them simpler and more efficient. For example:
it will make writing tools in different languages easier with the oss pprof support, as I only see async-profiler java jfr2pprof (which you use in JPProf) and your Go server parser for JFR. I have a node app (unfortunately) where I need to simulate some pyroscope api and I would like to receive pprof
apply a more efficient format early
provide flexibility to tradeoff parse performance overhead across the pipeline depending on the use case, for example offload large scale parse work to the distributed data plane where it may be more negligible.
I think this should be complementary to an agent capability grafana/alloy#395
The text was updated successfully, but these errors were encountered:
The pyroscope ecosystem is around Go pprof. I think it makes sense that the agent would be able to emit pprof natively in order to improve data flows that would operate on the canonical form. It can make them simpler and more efficient. For example:
I think this should be complementary to an agent capability grafana/alloy#395
The text was updated successfully, but these errors were encountered: