chuan-t/parca-agent

eBPF based always-on profiler auto-discovering targets in Kubernetes and systemd, zero code changes or restarts needed!

Parca Agent

Parca Agent is an always-on sampling profiler that uses eBPF to capture raw profiling data with very low overhead. It observes user-space and kernel-space stacktraces 19 times per second and builds pprof formatted profiles from the extracted data. Read more details in the design documentation.

The collected data can be viewed locally via HTTP endpoints and then be configured to be sent to a Parca server to be queried and analyzed over time.

Requirements

• Linux Kernel version 4.18+

Quickstart

See the Kubernetes Getting Started.

Supported Profiles

Profiles available for compiled languages (eg. C, C++, Go, Rust):

• CPU
• Soon: Network usage, Allocations

The following types of profiles require explicit instrumentation:

• Runtime specific information such as Goroutines

Debugging

Web UI

The HTTP endpoints can be used to inspect the active profilers, by visiting port 7071 of the process (the host-port that the agent binds to can be configured using the --http-address flag).

On a minikube cluster that might look like the following:

And by clicking "Show Profile" in one of the rows, the currently collected profile will be rendered once the collection finishes (this can take up to 10 seconds).

A raw profile can also be downloaded here by clicking "Download Pprof". Note that in the case of native stack traces such as produced from compiled language like C, C++, Go, Rust, etc. are not symbolized and if this pprof profile is analyzed using the standard pprof tooling the symbols will need to be available to the tooling.

Logging

To debug potential errors, enable debug logging using --log-level=debug.

Configuration

Flags:

Usage: parca-agent

Flags:
  -h, --help                      Show context-sensitive help.
      --log-level="info"          Log level.
      --http-address=":7071"      Address to bind HTTP server to.
      --node="hostname"           The name of the node that the process is
                                  running on. If on Kubernetes, this must match
                                  the Kubernetes node name.
      --config-path=""            Path to config file.
      --memlock-rlimit=0          The value for the maximum number of bytes of
                                  memory that may be locked into RAM. It is used
                                  to ensure the agent can lock memory for eBPF
                                  maps. 0 means no limit.
      --profiling-duration=10s    The agent profiling duration to use. Leave
                                  this empty to use the defaults.
      --profiling-cpu-sampling-frequency=19
                                  The frequency at which profiling data is
                                  collected, e.g., 19 samples per second.
      --metadata-external-labels=KEY=VALUE;...
                                  Label(s) to attach to all profiles.
      --metadata-container-runtime-socket-path=STRING
                                  The filesystem path to the container runtimes
                                  socket. Leave this empty to use the defaults.
      --local-store-directory=STRING
                                  The local directory to store the profiling
                                  data.
      --remote-store-address=STRING
                                  gRPC address to send profiles and symbols to.
      --remote-store-bearer-token=STRING
                                  Bearer token to authenticate with store.
      --remote-store-bearer-token-file=STRING
                                  File to read bearer token from to authenticate
                                  with store.
      --remote-store-insecure     Send gRPC requests via plaintext instead of
                                  TLS.
      --remote-store-insecure-skip-verify
                                  Skip TLS certificate verification.
      --remote-store-debuginfo-upload-disable
                                  Disable debuginfo collection and upload.
      --remote-store-batch-write-interval=10s
                                  Interval between batch remote client writes.
                                  Leave this empty to use the default value of
                                  10s.
      --debuginfo-directories=/usr/lib/debug,...
                                  Ordered list of local directories to
                                  search for debuginfo files. Defaults to
                                  /usr/lib/debug.
      --debuginfo-temp-dir="/tmp"
                                  The local directory path to store the interim
                                  debuginfo files.
      --debuginfo-strip           Only upload information needed for
                                  symbolization. If false the exact binary the
                                  agent sees will be uploaded unmodified.
      --debuginfo-upload-cache-duration=5m
                                  The duration to cache debuginfo upload exists
                                  checks for.
      --debuginfo-upload-timeout-duration=2m
                                  The timeout duration to cancel upload
                                  requests.

Roadmap

• Additional language support for just-in-time (JIT) compilers, and dynamic languages (non-exhaustive list):
  • Ruby
  • Node.js
  • Python
  • JVM
• Additional types of profiles:
  • Memory allocations
  • Network usage

Security

Parca Agent requires to be run as root user (or CAP_SYS_ADMIN). Various security precautions have been taken to protect users running Parca Agent. See details in Security Considerations.

To report a security vulnerability see this guide.

Contributing

Check out our Contributing Guide to get started!

License

User-space code: Apache 2

Kernel-space code (eBPF profilers): GNU General Public License, version 2

Credits

Thanks to:

• Aqua Security for creating libbpfgo (cgo bindings for libbpf), while we contributed several features to it, they have made it spectacularly easy for us to contribute and it has been a great collaboration. Their use of libbpf in tracee has also been a helpful resource.
• Kinvolk for creating Inspektor Gadget some parts of this project were inspired by parts of it.