alpha
Login
or
Join now
lass.pds.lassul.us
/
superconfig
Star
0
Fork
1
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
This repository has no description
Star
0
Fork
1
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
1
Pipelines
superconfig
/
configs
/
monitoring
/
dashboards
3 files
at
0c566f7bca24484ff67bcece22fd2d1b60dd390f
Hermes
configs.monitoring: use native VictoriaMetrics grafana datasource plugin
6d ago
8c7f5756
gatus.json
configs.monitoring: use native VictoriaMetrics grafana datasource plugin Grafana 13 no longer ships the prometheus datasource as a core plugin, so the provisioned VictoriaMetrics datasource was unusable. Switch it and the dashboards to victoriametrics-metrics-datasource.
6 days ago
logs.json
configs.monitoring: vector agents, victoria* + alertmanager stack on styx/coaxmetal Every NixOS machine runs Vector (host metrics, internal metrics, journal) and writes to VictoriaMetrics/VictoriaLogs on both styx and coaxmetal, each sink with a 512 MiB disk buffer. Both servers run vmalert (metrics and LogsQL instances), a two-node Alertmanager cluster posting to Matrix via matrix-alertmanager-receiver, Gatus (results scraped into VictoriaMetrics, alerted on by vmalert) and Grafana with provisioned datasources and dashboards. All ports are open on retiolum only. Replaces telegraf on neoprism, including the borgbackup status file.
6 days ago
node.json
configs.monitoring: use native VictoriaMetrics grafana datasource plugin Grafana 13 no longer ships the prometheus datasource as a core plugin, so the provisioned VictoriaMetrics datasource was unusable. Switch it and the dashboards to victoriametrics-metrics-datasource.
6 days ago