neolink VS retina

neolink on github

Thank you. I've just found this project that probably will cover my usecase: https://github.com/thirtythreeforty/neolink

might be worth checking this out. Haven't tried it myself, but was impressed by the writeup... and have been meaning to set one up in the homelab.

If you have battery powered cameras, my suggestion would be to use https://github.com/thirtythreeforty/neolink. Connect it to your own NVR(e.g. Shinobi, Frigate, etc.), and then apply whatever you need in terms of automations. For battery powered cameras... Yeah... I would love the same. The alternative is cumbersome, like using Relink email notifications for automating motion detection flows. Eventually I have thought of having a container that would be spun up after a motion detection email alert, to get the camera feed into my NVR. But I am sure that it would have a very high latency...

Yeah, excellent description of why the volume is so high, and when you're tracing a multithreaded one there's the additional noise from the way they're interleaved.

Besides filtering, I forgot to mention that some kind of aggregation/summary. strace flags are useful; even better to write a little program with eBPF (on Linux) or DTrace (on macOS/BSD/Solaris). I like being able to do stuff like this: https://github.com/scottlamb/retina/issues/5#issue-933945792

I suspected exactly that in this issue in one of my libraries, but when I actually looked with strace, I didn't see many syscalls returning EWOULDBLOCK. So then after that measurement, my new theory was that e.g. tokio::net::{Udp,Tcp}Socket would skip actually issuing the syscall if the mio layer hasn't returned availability since the last poll. Not true? Maybe I need to run my experiment again...

I'm plugging my new RTSP library retina into moonfire-nvr. But progress may be slow this week due to family obligations.