Tim Rühsen

`--no-robots` still fetches the robots.txt file because it may contain sitemaps. We can think of an option to disable sitemaps - in combination with `--no-robots`, robots.txt doesn't need to be...

> but there is very little data Is the samples timeline and/or the flamegraph empty or are you missing symbols? If you see frames from your app without further information...

> The issue seems specific to running within a container. Only kernel activity is shown. Reproduced via `docker exec` on Ubuntu VM. Just to clarify, the profiler is a system-wide...

Ideally, try running the docker container with something like ``` docker run --privileged --pid=host -v /etc/machine-id:/etc/machine-id:ro \ -v /var/run/docker.sock:/var/run/docker.sock -v /sys/kernel/debug:/sys/kernel/debug:ro ... ```

> Thanks, with those options it works in docker on Ubuntu. Thanks for testing. > I see all the information from the host too which isn't ideal, but better than...

@leonard520 Regarding the "Failed to probe tracepoint": Can you please update to the latest ebpf-profiler? The tracepoint check has been dropped meanwhile.

> @tmm1 I just tried the latest `main` branch. It still has the error "Failed to probe tracepoint". Does it come from [here](https://github.com/open-telemetry/opentelemetry-ebpf-profiler/blob/e3120e460aebcd3d5d29ec61d25f420bb28bcabd/internal/controller/controller.go#L46) Sorry, my fault. The code change I...

@leonard520 I assume that for some reason the unwinder runs into an error. Ideally, we could reproduce this somehow on amd64 (can you?). @fabled, maybe you can have look at...

@leonard520 I assume that you use devfiler for visualization. Can you run the profiler with `-send-error-frames`? I assume that you see the error frames in red directly under the root...

> I am wondering if this is a problem. No this is not a problem. I made a test where I changed the code to look into `cgroupxxx` here, to...