grafana/pyroscope

★ 11,428GoAudience · ops devopsComplexity · 4/5Setup · moderate

Mindmap

mindmap
  root((pyroscope))
    What it does
      Continuous profiling
      CPU and memory tracking
    How it works
      Server plus agents
      SDK per language
      Grafana Alloy pull
    Languages
      Go Java Python Ruby
      Node.js Rust dotNET
    Deployment
      Local Docker
      Grafana Cloud
      Kubernetes Helm
    Use cases
      Reduce CPU usage
      Fix memory leaks
      Debug slow requests

mindmap root((pyroscope)) What it does Continuous profiling CPU and memory tracking How it works Server plus agents SDK per language Grafana Alloy pull Languages Go Java Python Ruby Node.js Rust dotNET Deployment Local Docker Grafana Cloud Kubernetes Helm Use cases Reduce CPU usage Fix memory leaks Debug slow requests

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Attach the Pyroscope SDK to a Go or Python service to identify which functions consume the most CPU during a live incident.

USE CASE 2

Use Pyroscope on a Kubernetes cluster to proactively reduce memory usage before it causes outages.

USE CASE 3

Set up Grafana Alloy to pull profiling data from services automatically without modifying their source code.

USE CASE 4

Connect to Grafana Cloud to get profiling dashboards without running your own Pyroscope server.

Tech stack

GoDockerKubernetesGrafanaeBPFHelm

Getting it running

Difficulty · moderate Time to first run · 30min

Full cluster profiling requires Kubernetes and Helm setup, local single-service testing works with a single Docker command.

No license information was mentioned in the explanation.

In plain English

Grafana Pyroscope is a tool for continuous profiling, which means it watches running applications and collects data about what they are spending their time and memory on. This kind of monitoring helps engineering teams find performance problems: for example, why a service is using too much CPU, why memory keeps growing, or why certain requests are slow. Pyroscope works by pairing a server with small client-side agents or SDKs that run inside your application. The agents collect profiling data and send it to the Pyroscope server, which stores and processes it. You can then explore the results through a visual interface called Explore Profiles, which is part of the Grafana observability platform. The interface does not require writing queries, you browse through services and time ranges and drill into specific functions to see where time is being spent. The tool supports a wide range of programming languages. You can attach an SDK or agent to applications written in Go, Java, Python, Ruby, Node.js.NET, Rust, and others. It can also be configured to pull profiling data automatically via Grafana Alloy, without modifying application code. For deployment, Pyroscope can be run locally via Homebrew or Docker in a single command. It is also available as a managed service through Grafana Cloud, where no server setup is required. For teams running their own infrastructure, deployment on Kubernetes is documented separately. The typical use cases are proactive ones, such as reducing resource consumption before a problem occurs, and reactive ones, such as diagnosing an active incident with line-level detail about what code is running.

Copy-paste prompts

Prompt 1

I have a Go service that is using too much CPU in production. Show me how to add the Pyroscope Go SDK so I can see a flame graph of where time is being spent.

Prompt 2

How do I deploy Pyroscope on Kubernetes using Helm so my team can profile all services in a cluster without code changes?

Prompt 3

My Python web app has a memory leak. Walk me through connecting it to Pyroscope and reading the allocation profile to find which function is holding memory.

Prompt 4

I want to try Pyroscope locally before committing to a deployment. Show me the single Docker command to start the server and send a test profile.

Open on GitHub → Explain another repo

← grafana on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.