Monitoring Frigate with Zabbix #9066
leccelecce
started this conversation in
Show and tell
Replies: 3 comments
-
In Zabbix 6.0 adjusting template, but the discovery list / Camera Discovery dont work...
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Just found out about that. Might give it a try (but I'm using Zabbix V7. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I use Zabbix at home for power/network/server/IP camera/VM/docker/application monitoring/dashboards/alerting. For those not familiar with it, best look here: https://www.zabbix.com/documentation/current/en/manual/introduction/features. This is about application/hardware monitoring, not monitoring the actual video or motion/object events from Frigate.
I've configured an HTTP template for use with Frigate 0.13 (tested against beta7) which I intend to submit to the Zabbix community templates site. Dynamic discovery rules have been set up to auto-detect cameras, storage paths, detectors and GPUs so there is no hard-coding - it should work on anyone's setup. It uses Frigate's
/api/stats
HTTP endpoint, so just needs your Frigate hostname and the port if you're not using the default of 5000. There might be a few items which are not monitored e.g. I have an Intel GPU, but not NVIDIA, so the GPU stats I'm using are a bit more basic. I'll probably take a look at the stats code to see how non-Intel bits are structured at some point and update.I know the Home Assistant add-on allows you to do much the same (if not more, because it subscribes to a broader range of MQTT topics), which is no doubt fine for some people. But if you're monitoring a reasonable amount of non-smart home hardware, you're probably not doing that in HASS, and I certainly prefer to have everything centralised.
The YAML is here which you can easily import into Zabbix UI.
https://gist.github.com/leccelecce/01cb0adeb57a21bc232c0067bb7b9d3c
In terms of what this looks like, below is what I've set up recently for three test cameras. Note that two components (hardware load average and disk response times) come not from Frigate but from the standard Zabbix Linux agent.
Raw data items, auto-discovered:
Zabbix also allows configurable triggers for problem alerting. A few standard ones are included. I'm looking at setting some additional ones to monitor (e.g. unexpected zero FPS from a camera), but I need to play around with the stats API a bit more and might need to send PRs to add the odd bit of data (or add in some other API calls).
If anyone else is using Zabbix 6.4+ and tries it out, all feedback welcome.
Beta Was this translation helpful? Give feedback.
All reactions