• Sources: primary
  • Summary: Grafana Labs says the Pyroscope Python SDK now supports memory profiling with mem_enabled=True, and the Rust SDK reports in-use memory through the jemalloc allocator. .NET profiling on Windows x64 is in public preview from profiler 1.3.0. The gcx Grafana CLI gains gcx profiles commands that rank services by a profile type, list exemplar profiles and export pprof files, and the Grafana UI adds exemplars and a Call Tree view.
  • Why it matters: Rust and Python services can now be checked for heap growth and leaks in the same Pyroscope stack that already holds their CPU profiles.
  • Background: Continuous profiling samples stack traces from running services all the time and stores them so engineers can see where CPU time and memory go across a fleet. A CPU profile shows where code spends time, while an in-use memory profile shows which call paths allocated memory that is still live, which is what points at a leak. Exemplars are individual profiles from single processes, so one bad instance does not disappear into an aggregate.