-
# Add pprof labels for better CPU profiling insights
## Background
When using pprof for CPU/memory profiling in Hugo (`--profile-cpu`, `--profile-mem`), the flamegraph output doesn't allow for a d…
-
Please answer these questions before submitting your issue. Thanks!
### What version of pprof are you using?
If you are using pprof via `go tool pprof`, what's your `go env` output?
If you run …
-
This simple program panics on recent toolchains
```
use pyroscope::PyroscopeAgent;
use pyroscope_pprofrs::{pprof_backend, PprofConfig};
fn main() {
let pprof_config = PprofConfig::new().s…
-
### What's wrong?
Attempting to run alloy 1.3.1 produces the following error:
```
panic: pattern "GET /debug/pprof/" (registered at /usr/lib/go/src/net/http/pprof/pprof.go:100) conflicts with pat…
-
The standard pprof export via the UI returns the full profile, which easily exceeds 100MB in size and is practically unusable. Not to mention, such a query typically crashes the queriers and the query…
-
```
#!watchflakes
default
-
### What's wrong?
Conflicting patterns detected when built with Go 1.23
````
$ grafana-agent --version
panic: pattern "GET /debug/pprof/" (registered at net/http/pprof/pprof.go:100) conflict…
-
**Which component are you using?**:
vertical-pod-autoscaler
vpa-admission-controller
**Is your feature request designed to solve a problem? If so describe the problem this feature should solv…
-
### Version
None
### Is your feature request related to a problem? Please describe.
Need deeper insight to debug resource consumption and performance issues in Gloo Fed control plane.
### Describe…
-
```
#!watchflakes
default