Closed sandeepkoseai closed 3 months ago
Hi @sandeepkoseai, everything looks correct from your steps. We need to enable a bit more logging to see what's happening.
Can you please add the following two environment options and send us the Beyla output:
export BEYLA_LOG_LEVEL=debug
export BEYLA_BPF_DEBUG=1
Run one or two curl commands like you did before.
This will print a lot more and we should be able to tell what's not working or what's misconfigured.
Hi Nikola,
Thanks for the quick response, here is the complete logs as requested:
@.:~# echo $BEYLA_LOG_LEVEL && echo $BEYLA_BPF_DEBUG
debug
1
@.:~# sudo -E beyla
time=2024-08-15T16:13:48.846Z level=INFO msg="Grafana Beyla" Version=v1.7.0
Revision=9d07bfb "OpenTelemetry SDK Version"=1.28.0
time=2024-08-15T16:13:48.847Z level=DEBUG msg="not reporting internal
metrics"
time=2024-08-15T16:13:48.847Z level=DEBUG msg="trying to fetch host ID"
component=ContextInfo func=fetchHostID fetcher=AWS
time=2024-08-15T16:13:48.849Z level=INFO msg="got host ID"
component=ContextInfo func=fetchHostID fetcher=AWS
hostID=i-0ea5b51aa1675a5c6
time=2024-08-15T16:13:48.849Z level=INFO msg="starting Beyla in Application
Observability mode"
time=2024-08-15T16:13:48.849Z level=DEBUG msg="Linux kernel version"
component=nethttp.Tracer major=6 minor=8
time=2024-08-15T16:13:48.849Z level=DEBUG msg="checking kernel lockdown
mode, [none] allows us to propagate trace context"
component=ebpf.ProcessTracer
time=2024-08-15T16:13:48.849Z level=DEBUG msg="Kernel not in lockdown mode,
trace context propagation is supported." component=nethttp.Tracer
time=2024-08-15T16:13:48.849Z level=DEBUG msg="Linux kernel version"
component=grpc.Tracer major=6 minor=8
time=2024-08-15T16:13:48.849Z level=DEBUG msg="checking kernel lockdown
mode, [none] allows us to propagate trace context"
component=ebpf.ProcessTracer
time=2024-08-15T16:13:48.849Z level=DEBUG msg="Kernel not in lockdown mode,
trace context propagation is supported." component=grpc.Tracer
time=2024-08-15T16:13:48.849Z level=DEBUG msg="mounting BPF map pinning"
component=discover.TraceAttacher path=/var/run/beyla/beyla-958378
time=2024-08-15T16:13:48.849Z level=DEBUG msg="BPF map pinning path does
not exist. Creating before mounting" component=discover.TraceAttacher
time=2024-08-15T16:13:48.851Z level=DEBUG msg="creating instrumentation
pipeline" component=beyla.Instrumenter
time=2024-08-15T16:13:48.851Z level=DEBUG msg="starting criteria matcher
node" component=discover.CriteriaMatcher
time=2024-08-15T16:13:48.852Z level=DEBUG msg="loading independent eBPF
program" component=ebpf.ProcessTracer
time=2024-08-15T16:13:48.855Z level=DEBUG msg="found FQDN hosts"
component=HostnameResolver
hosts=[ip-172-31-43-47.us-east-2.compute.internal.]
time=2024-08-15T16:13:48.855Z level=DEBUG msg="Notifying observers"
component=HostnameResolver change=2
time=2024-08-15T16:13:48.855Z level=INFO msg="using hostname"
component=traces.ReadDecorator function=instance_ID_hostNamePIDDecorator
hostname=ip-172-31-43-47.us-east-2.compute.internal
time=2024-08-15T16:13:48.856Z level=INFO msg="Starting main node"
component=beyla.Instrumenter
time=2024-08-15T16:13:48.958Z level=DEBUG msg="going to add kprobe to
function" component=ebpf.Instrumenter probes=kprobes function=sys_bind
probes="{Required:true Start:Kprobe(kprobe_sys_bind)#3 End:
time=2024-08-15T16:14:54.214Z level=DEBUG msg="=== sock alloc e9f9e000e9f9e ===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.214Z level=DEBUG msg="=== accept 4 ret id=958366, sock=ffff92ea566b1380, fd=27 ===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.215Z level=DEBUG msg="=== tcp_recvmsg id=958366 sock=ffff92eb4cdb8a00 ===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.215Z level=DEBUG msg="=== tcp_recvmsg ret id=958366 sock=ffff92eb4cdb8a00 copied_len 80 ===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.215Z level=DEBUG msg="msg iter type exists, read value 0" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.215Z level=DEBUG msg="iter type 0" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.215Z level=DEBUG msg="new kernel, iov doesn't exist, nr_segs 1" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.215Z level=DEBUG msg="standard iov 62818dfcb2b0 base 6f6f662f20544547 len 1414809632" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.215Z level=DEBUG msg="buf=[], pid=958366, len=80" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="=== kprobe tcp_sendmsg=958366 sock=ffff92eb4cdb8a00 size 241===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="msg iter type exists, read value 1" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="iter type 1" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="new kernel, iov doesn't exist, nr_segs 3" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="standard iov ffff9ea7ecadfd70 base 62818e05de40 len 233" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="buf=[HTTP/1.1 200 OK\r\nX-Power\xe0|\x8f\xbf\xa7\xbe\xff\xff\xf1], pid=958366, len=241" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="No info, pid =958366?, looking for fallback..." component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="=== http_buffer_event len=241 pid=958366 still_reading=1 ===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="Delaying finish http for large request, orig_len 241" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="=== tcp_rcv_established id=958366 ===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="=== tcp_rcv_established id=958366 ===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="=== kretprobe tcp_sendmsg=958366 sent 241===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="=== tcp_recvmsg id=958366 sock=ffff92eb4cdb8a00 ===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="Checking if we need to finish the request per thread id" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.216Z level=DEBUG msg="Checking if we need to finish the request per socket" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.217Z level=DEBUG msg="=== kprobe tcp_close 958366 sock ffff92eb4cdb8a00 ===" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.217Z level=DEBUG msg="Checking if we need to finish the request per thread id" component=BPFLogger pid=958366 comm=node time=2024-08-15T16:14:54.217Z level=DEBUG msg="Checking if we need to finish the request per socket" component=BPFLogger pid=958366 comm=node
Best & Regards, Sandeep
On Thu, Aug 15, 2024 at 6:37 PM Nikola Grcevski @.***> wrote:
Hi @sandeepkoseai https://github.com/sandeepkoseai, everything looks correct from your steps. We need to enable a bit more logging to see what's happening.
Can you please add the following two environment options and send us the Beyla output:
export BEYLA_LOG_LEVEL=debug export BEYLA_BPF_DEBUG=1
Run one or two curl commands like you did before.
This will print a lot more and we should be able to tell what's not working or what's misconfigured.
— Reply to this email directly, view it on GitHub https://github.com/grafana/beyla/issues/1093#issuecomment-2291235799, or unsubscribe https://github.com/notifications/unsubscribe-auth/BKRSU5ANZR2R2HSRYIB4AVLZRSR2HAVCNFSM6AAAAABMR3I22KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJRGIZTKNZZHE . You are receiving this because you were mentioned.Message ID: @.***>
Ah this is the issue we just fixed few days ago with kernel versions 6.7 and newer. Are you able to try our main branch?
The PR that resolved the problem is this one https://github.com/grafana/beyla/pull/1086. CC @rafaelroquetto
Hi Nikola,
Here is the branch details I am currently using:
@.:/home/ubuntu/belya# git remote -v origin https://github.com/grafana/beyla.git (fetch) origin https://github.com/grafana/beyla.git (push) @.:/home/ubuntu/belya# git status On branch main Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
Please let me know if any additional information is required.
Best & regards, Sandeep
On Thu, Aug 15, 2024 at 11:12 PM Nikola Grcevski @.***> wrote:
Ah this is the issue we just fixed few days ago with kernel versions 6.7 and newer. Are you able to try our main branch?
The PR that resolved the problem is this one #1086 https://github.com/grafana/beyla/pull/1086. CC @rafaelroquetto https://github.com/rafaelroquetto
— Reply to this email directly, view it on GitHub https://github.com/grafana/beyla/issues/1093#issuecomment-2291839171, or unsubscribe https://github.com/notifications/unsubscribe-auth/BKRSU5HOPSVSRT5FCL2W56TZRTSB7AVCNFSM6AAAAABMR3I22KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJRHAZTSMJXGE . You are receiving this because you were mentioned.Message ID: @.***>
Hi @sandeepkoseai, are you able to post the SHA1 of the branch HEAD commit just so that we can be sure about what we are dealing with?
You can do it with git rev-parse HEAD
.
Thanks!
He Fafael,
Please find suggested commands output below:
$ git rev-parse HEAD ef146163253d6644e3b4db861ea8eb130ca7fdb2
Please let me know if any additional information is required.
Best & regards, Sandeep Kose
On Fri, Aug 16, 2024 at 7:00 PM Rafael Roquetto @.***> wrote:
Hi @sandeepkoseai https://github.com/sandeepkoseai, are you able to post the SHA1 of the branch HEAD commit just so that we can be sure about what we are dealing with? You can do it with git rev-parse HEAD. Thanks!
— Reply to this email directly, view it on GitHub https://github.com/grafana/beyla/issues/1093#issuecomment-2293515863, or unsubscribe https://github.com/notifications/unsubscribe-auth/BKRSU5EFQRHBGFLLCQB6NCTZRX5IRAVCNFSM6AAAAABMR3I22KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJTGUYTKOBWGM . You are receiving this because you were mentioned.Message ID: @.***>
Hi @sandeepkoseai,
Based on what Beyla showed in the log, the build revision that's running is "9d07bfb". When you downloaded the "main" branch, if you built it with make
, the new Beyla executable will be in bin/beyla
. I wonder if it's simply an issue that you are still picking up the old 1.7.0 branch of Beyla?
When you run Beyla we print the git hash as the first line in the version, e.g.:
time=2024-08-15T16:13:48.846Z level=INFO msg="Grafana Beyla" Version=v1.7.0
Revision=9d07bfb "OpenTelemetry SDK Version"=1.28.0
Hi Nikola,
I performed a fresh clone on the main branch and ran the make
command, but I encountered several issues. Here are the details:
1. Initial Error: llvm-strip
Not Found
go generate ./pkg/...
Error: exec: "llvm-strip": executable file not found in $PATH
pkg/internal/ebpf/common/common.go:23: running "/home/ubuntu/beyla/bin/bpf2go": exit status 1
Error: exec: "llvm-strip": executable file not found in $PATH
pkg/internal/ebpf/goredis/goredis.go:32: running "/home/ubuntu/beyla/bin/bpf2go": exit status 1
...
make: *** [Makefile:152: generate] Error 1
sudo apt-get install llvm -y
2. Subsequent Error: clang
Not Found
go generate ./pkg/...
Error: compile: exec: "clang": executable file not found in $PATH
pkg/internal/ebpf/common/common.go:23: running "/home/ubuntu/beyla/bin/bpf2go": exit status 1
Error: compile: exec: "clang": executable file not found in $PATH
pkg/internal/ebpf/goredis/goredis.go:32: running "/home/ubuntu/beyla/bin/bpf2go": exit status 1
...
make: *** [Makefile:152: generate] Error 1
sudo apt-get install clang -y
3. Current Issue: Test Failures
coverage: 8.5% of statements in ./...
FAIL github.com/grafana/beyla/pkg/internal/ebpf/common 0.178s
ok github.com/grafana/beyla/pkg/internal/ebpf/httpfltr 1.179s coverage: 0.3% of statements in ./...
...
FAIL
make: *** [Makefile:184: test] Error 1
Could you please assist with resolving the test failures (#3) or provide the bin/beyla
package, if possible?
Best regards,
Sandeep Kose
Hi @sandeepkoseai, you can ignore the test failures, if you'd like you can also just run make dev
which will build without the tests.
We've also made a pre-release with the fixes here, so you can instead pull the binaries directly https://github.com/grafana/beyla/releases
Hello Team,
Thank you for your help! The issue has been resolved with the release of version v1.7.1-alpha.1.
Hello Team,
I am experiencing issues with Grafana Beyla when trying to trace logs for a Node.js service on Ubuntu. I followed the Node.js Quickstart guide but am not seeing any traces in Beyla despite performing all steps as instructed.
Here are the specifics of my environment and the steps I’ve followed:
Environment:
Steps Taken:
Run an Instrumentable Node.js Service:
Download Beyla: Downloaded the latest Beyla executable from the Beyla releases page. Uncompressed and placed the Beyla executable in my
$PATH
.Run Beyla with Minimal Configuration:
Test the Service: With Beyla and the Node.js service running, I made an HTTP request:
Expected Output: Beyla should output traces to the standard output, similar to:
Current Issue: I am not receiving any trace output in the Beyla console after making the HTTP request, even waited for sometime. The Beyla console output after starting is:
Request for Assistance: Please let me know if there are any additional steps I should take or if there is something I might be missing.