rob-scheepens comments

Results 43 comments of


                                            rob-scheepens

Feature: implement vRDMA

I suspect implementing NDK support is the first step towards this, see https://docs.microsoft.com/en-us/windows-hardware/drivers/network/initializing-an-ndk-capable-miniport-driver.

Flamegraph error when passing it what seems like a valid folded file

Same issue on Debian Bullseye: ``` root@rob-prom-graf:~/git/FlameGraph# perf sched record -g -a -- sleep 1 [ perf record: Woken up 1 times to write data ] [ perf record: Captured...

Flamegraph error when passing it what seems like a valid folded file

The tip from https://github.com/brendangregg/FlameGraph/issues/150#issuecomment-338448925 worked on my Debian system, but not on my SLES12SP5 system (kernel 4.12.14-122.116-default).

Flamegraph error when passing it what seems like a valid folded file

Same issue with SLES15SP3: ``` hana-g8-vm-sles15sp3:~/git/FlameGraph # uname -r 5.3.18-150300.59.63-default hana-g8-vm-sles15sp3:~/git/FlameGraph # cat /proc/sys/kernel/sched_schedstats 1 ``` Still a 0 bytes file: ``` hana-g8-vm-sles15sp3:~/git/FlameGraph # ./stackcollapse-perf-sched.awk g8-vm > g8-vm.folded hana-g8-vm-sles15sp3:~/git/FlameGraph #...

terminate called after throwing an instance of 'std::bad_function_call'

Getting a similar crash when clicking metrics from the web page after starting the exporter: ```nutanix@NTNX-S319428X8905436-B-CVM:10.56.6.32:~$ sudo /usr/bin/ebpf_exporter --config.file /home/nutanix/bio.yaml 2022/02/01 09:57:41 Starting with 1 programs found in the config...

terminate called after throwing an instance of 'std::bad_function_call'

Setting up core dump gives: ```panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0x7804ae] goroutine 1 [running]: debug/elf.(*Prog).Open(...) /usr/lib/golang/src/debug/elf/file.go:166 github.com/go-delve/delve/pkg/proc/core.readNotes(0x7fffa7c82721, 0xf2c7) /root/delve/pkg/proc/core/linux_core.go:228...

terminate called after throwing an instance of 'std::bad_function_call'

Solved by building bcc from source and copying /usr/lib64/libbcc* binaries to the problematic machine.

First implementation of physical_disk collector

> Nice! Some feedback below. Also the CI is failing because you added it as a default collector, which means the end-to-end tests need to be updated (see [tools/e2e-output.txt](https://github.com/prometheus-community/windows_exporter/blob/master/tools/e2e-output.txt)) What...

First implementation of physical_disk collector

@carlpett : I've modified e2e-output and included it in this PR. Can you check if all is ok now?

First implementation of physical_disk collector

> Thanks! The e2e test appear to fail now though, although it's not clear to me why. Do they work locally for you? When I execute "C:\git\rob-scheepens\windows_exporter>powershell -NonInteractive -ExecutionPolicy Bypass...