Set up Parca agent for continuous CPU profiling of systemd services and query profiles using the Parca UI and API

domain: parca.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Deploy the Parca server and configure object storage for profile persistence in the parca.yaml config file
  2. Deploy parca-agent as a DaemonSet or systemd service with the --node flag and grant CAP_SYS_ADMIN and CAP_PERFMON capabilities for eBPF profiling
  3. Set --remote-store-address to the Parca gRPC endpoint so the agent streams profiles to the server in real time
  4. Open the Parca UI and use the profile selector to choose a service and time range, then inspect the flamegraph
  5. Query profiles programmatically via the Parca QueryService gRPC API using the QueryRange RPC with a label matcher and time window

Known gotchas

Related routes

Deploy Parca Agent as a Kubernetes DaemonSet for continuous eBPF-based whole-system profiling and query the collected profiles via the Parca server's API/UI in pprof format
parca.dev · 6 steps · unrated
Deploy Parca for continuous profiling with pprof scraping from Go services
parca.dev · 5 steps · unrated
Query continuous profiling data from Parca using the gRPC API and profile query language
www.parca.dev · 6 steps · unrated

Give your agent this knowledge — and 15,800+ more routes

One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans