In this article
What changed
The Pyroscope Python SDK now supports memory profiling. It shows which code allocates the most memory and which allocated memory is still in use. Enable it with mem_enabled=True in pyroscope.configure.
The Rust SDK also gains memory profiling, through the jemalloc allocator. It reports in-use memory so you can track heap growth and leaks. .NET profiling now runs on Windows x64 as a public preview, including .NET Framework apps hosted in IIS.
Grafana also added exemplars and a new Call Tree view for exploring profiles. The gcx CLI gains gcx profiles commands for querying Pyroscope. For example, gcx profiles metrics --top ranks services by a profile type over a time window. Commands here come from the documentation listed under Sources; check them against your own setup before running them.
Who needs to act
Exemplars require the v2 storage layer that Pyroscope 2.0 is built on, so check which storage layer your deployment uses before you expect them. For Windows .NET profiling, you need x64 and profiler version 1.3.0 or later. On .NET 8, 9 and 10 you get the same profile types as on Linux, with the same environment variables. On .NET Framework 4.7 and later, CPU and wall-time profiling are available.
gcx turns on agent mode automatically in many coding agents, such as Claude Code, GitHub Copilot and Cursor. Other agents can use the --agent flag. Grafana says Pyroscope 2.0 cut symbol storage by up to 95% in its own production environment. That figure is vendor-measured.
What the sources don't cover
The material we reviewed gives no release dates, minimum SDK versions or details on allocators other than jemalloc, so check the Grafana announcement for those.
Sources
This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].
Discussion