Add bitcoind-pid parameter to ebpf-extractor

[lucasaafaria]

Description: takes the $BITCOIND_PID value and pass it as bitcoind-pid parameter to the ebpf-extractor initialization command.

Expected results: ebpf-extractor initializes correctly and connects to the correct node.

closes #21

[m4ycon]

It seems correct but for some reason logger isn't receiving any messages from nats, it logs a lot of messages when its working. I wonder if this PID is correct, which I don't see any reason not to be.

[0xB10C]

I found the tool nats-top helpful when debugging NATS related stuff. Alternatively, you can run the ebpf-extractor with RUST_LOG=trace.

[lucasaafaria]

I found the tool nats-top helpful when debugging NATS related stuff. Alternatively, you can run the ebpf-extractor with RUST_LOG=trace.

Using nats-top, it seems that NATS isn't getting any message published to it, and thus logger doesn't have anything to show from it. I'll try running the ebpf-extractor with trace log level and see if I can figure out why this is happening.

[0xB10C]

Is the bitcoind connected to the network and communicating with peers? If you run bitcoind in regtest, there might be no messages to extract if you don't have any peers.

[lucasaafaria]

With this last change, the ebpf-extractor uses the correct pid, and logger works correctly.

Logger messages when there is ongoing traffic between peers:

[m4ycon]

Nice one! It worked fine here 👍