Dustin
a87b53e3ac
At some point this week, the front porch camera stopped sending video. I'm not sure exactly what happened to it, but Frigate kept logging "Unable to read frames from ffmpeg process." I power-cycled the camera, which resolved the issue. Unfortunately, no alerts were generated about this situation. Home Assistant did not consider the camera entity unavailable, presumably because Frigate was still reporting stats about it. Thus, I missed several important notifications. To avoid this in the future, I have enabled the "Camera FPS" sensors for all of the cameras in Home Assistant, and added this alert to trigger when the reported framerate is 0. I really also need to get alerts for log events configured, as that would also indicated there was an issue. |
||
|---|---|---|
| .. | ||
| README.md | ||
| alertmanager-ntfy.config.yml | ||
| alertmanager-ntfy.yaml | ||
| alertmanager.config.yml | ||
| alertmanager.yaml | ||
| alerts.yml | ||
| blackbox-exporter.yaml | ||
| blackbox.yml | ||
| ingress.yaml | ||
| kustomization.yaml | ||
| namespace.yaml | ||
| recording.yml | ||
| scrape.yml | ||
| secrets.yaml | ||
| vmagent.yaml | ||
| vmalert.yaml | ||
| vminsert.yaml | ||
| vmselect.yaml | ||
| vmstorage-iscsi.yaml | ||
| vmstorage.yaml | ||
README.md
Victoria Metrics
Victoria Metrics is a powerful, scalable time-series database compatible with Prometheus and its ecosystem of metrics exporters.
Clustered Deployment
Victoria Metrics can run in a high-availability cluster, with the various functions of the TSDB split into independently-scalable processes:
vmstorage: Stores time series data.vminsert: Ingests metrics in various formats (e.g. Prometheus) and sends them to one or morevmstoragenodes.vmselect: Performs metrics queries, retrieving results from one or morevmstoragenodes.
The vmstorage processes are managed by a StatefulSet with a volume claim
template for persistent storage. The number of replicas in the StatefulSet
must be 2n-1 where n is the value of the replicationFactor setting for
vminsert.
vminsert and vmselect processes are stateless and thus managed by a
Deployment. There should be at least 2 replicas of each of these, so that
restarts, etc. can be performed without any downtime.
vmagent
In a typical Victoria Metrics ecosystem, collecting metrics is handled
separately from the TSDB. The vmagent process handles scraping and receiving
metrics and passing them to vminsert. vmagent can cache received metrics
locally, in case no vminsert process is available, so it requires persistent
storage and is therefore managed by a StatefulSet. Because there are multiple
vmagent processes scraping the same targets, the vminsert and vmstorage
processes MUST have the dedup.minScrapeInterval setting set to match the
vmagent scrape interval. Jobs with scrape intervals longer than the
default will unfortunately have duplicate data points.
Blackbox Exporter
Many applications and web sites are monitored via the Blackbox Exporter, which makes arbitrary HTTP, TCP, ICMP, etc. requests and reports Prometheus metrics about them. This is a stateless process, managed by a Deployment.
vmalert
Victoria Metrics has a separate process for alerting, vmalert. This process periodically executes the queries defined in its alerting rules and creates alerts for matching results. Alerts are stored in the Victoria Metrics TSDB. Rules are defined in a YAML document, managed by a ConfigMap. Notifications are sent to Alertmanager.
Alertmanager
Alertmanager receives notifications from vmalert and sends e.g. email
messages. Multiple instances can be run in a cluster; each node needs to know
the host and port of every node in the cluster.