You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a weird situation where I am running a pod with two containers, one Python service and one Golang service. The Golang service is being detected and instrumented, however I am not seeing any metrics or traces for the Python service.
The Python service in question is run using uvicorn, and ps -ef on the host gives the following:
I have a hunch its because the non-debug logs are finding a python3.12 process, but the logs are saying comm=uvicorn. But this is about as deep as my knowledge goes. Please let me know if I can help somehow.
The text was updated successfully, but these errors were encountered:
I have a weird situation where I am running a pod with two containers, one Python service and one Golang service. The Golang service is being detected and instrumented, however I am not seeing any metrics or traces for the Python service.
The Python service in question is run using
uvicorn
, andps -ef
on the host gives the following:I am running this pod in k3s on a Raspberry Pi 5, compiled with the following settings: https://www.gouthamve.dev/building-the-raspberry-pi-kernel-for-ebpf-beyla/
I am running Beyla
v1.9.4
.Beyla Config:
Default logs:
Debug logs filtered on "pid=3073"
I've also noticed this interesting line:
Its coming from this function which seems to exclude the data from the process entirely:
beyla/pkg/internal/ebpf/common/pids.go
Lines 124 to 159 in 0cef675
Removing the
routes:
section and applying this diff didn't fix the issue:I have a hunch its because the non-debug logs are finding a
python3.12
process, but the logs are sayingcomm=uvicorn
. But this is about as deep as my knowledge goes. Please let me know if I can help somehow.The text was updated successfully, but these errors were encountered: