Tolya Korniltsev
Tolya Korniltsev
In ebpf we do "ebfp/namespace/container" We should have something similar for java , so that targets do not get merged to "unspecified" in k8s ever
When agent is run without privileged securityContext, the profiler shows this error ``` level=error msg="component exited with error" component=pyroscope.ebpf.local_pods err="ebpf profiling session start: load bpf objects: field DisassociateCtty: program disassociate_ctty:...
-pid=host does not work in kind and it runs in a separate pid namespace https://github.com/kubernetes-sigs/kind/issues/3182 If the pods are running as privileged(I am not 100% sure) we may consider adding...
Add introduction to godoc explaining what it is and why it is needed https://pkg.go.dev/github.com/pyroscope-io/godeltaprof The current docs have docs for the structures and APIs but not for the whole package
hgrun is doing some symlinks across containers via /proc/{pid}/root/... and that confuses profiler and profiler cant open plugin files https://ops.grafana-ops.net/goto/CTbuPbHIR?orgId=1
``` │ ts=2023-11-28T07:57:10.469825102Z level=error msg="updating pids map" component=pyroscope.ebpf.instance err="update: key too big for map: argument list too long" ``` I've noticed this error, it should not happen.
Og pyroscope supported reading symbols from perf map, grafana pyroscope should also do it https://github.com/iovisor/bcc/blob/bc9b43a00b83bcea600b3540c5a6124ebd78a7ff/src/cc/bcc_perf_map.c#L25
currently session.go has zero tests and is quite complex we should improve, - maybe hide cilium/ebpf behind interfaces - maybe search internet if someone already done smth similar
#### PR Description This PR changes pyroscope.scrape behavior to do "godeltaprof probing" at the very beginning of target scrape. What godeltaprof probing mean is when a component configured to scrape...
It looks like right now it is not possible to configure compression level of the underlying Deflater. I suspect someone might want to do it to save some cpu/latency/bandwidth (for...