@NickM-27 commented on GitHub (Dec 29, 2024):
Please create a support discussion
@NickM-27 commented on GitHub (Dec 29, 2024):
You can already limit recording retention and snapshot retention and those are the main users of storage.
There is already a separate feature…
@NickM-27 commented on GitHub (Dec 29, 2024):
Frigate already runs a health check on go2rtc, perhaps we can add more checks to this but that can cause false positive restarts. I'm not sure if an…
@esand commented on GitHub (Dec 29, 2024):
Ok, that's quite interesting that it has its own health checks, because just now I checked my instance of Frigate and it was reporting 230% cpu usage,…
@NickM-27 commented on GitHub (Dec 29, 2024):
Does the health check still get used if someone has a custom go2rtc binary (as I do in my case)? Perhaps that's the issue?
Yes it works regardless.…
@hawkeye217 commented on GitHub (Dec 29, 2024):
I'm with @NickM-27, the benefits don't outweigh the risks with possible security implications and the fact that it's addressing a symptom rather…
@esand commented on GitHub (Dec 30, 2024):
Not to beat a dead horse, but are there security implications with the existing Frigate restart API call that exists? I believe you can even just…
@hawkeye217 commented on GitHub (Dec 27, 2024):
What version of Frigate are you using?
@NickM-27 commented on GitHub (Dec 26, 2024):
Yes, some users have reported it's already working for Intel. Amd will be more difficult and we'll have to see what can be supported
@hawkeye217 commented on GitHub (Dec 27, 2024):
There is already timeouts and reconnect logic in place for streams that use go2rtc. We use an [external package](https://github.com/cycjimmy/jsmpeg-…