social.dk-libre.fr is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Does anyone use Prometheus webhook notifications with XMPP, specifically Prosody? There seem to be several ways of doing it but I'm struggling to get any of them to work. Any help would be welcome. TIA #prometheus #xmpp #webhook #prosodyim
🚀 Running 100M+ active series is no small feat.
From #Prometheus to #VictoriaMetrics: how it measures up against# Mimir. Trade Republic runs 100M+ active series across several clusters. This short talk walks through why we moved off Prometheus, the topology we landed on, and a side-by-side #benchmark comparing Mimir and VictoriaMetrics across ingestion, query latency, CPU/RAM/network, and the operational reality of running each.
Watch it on demand! 🎥
https://bit.ly/4g7nqQd
VictoriaMetrics v1.147.0:
- Easier migration from single-node to cluster
- New #MDX routing in #vmagent
- Enhanced authentication, aggregation, and performance improvements.
Read the latest updates and discover what's new across the #VictoriaMetrics ecosystem
https://bit.ly/4fOHlV4
🚀 Did you miss our latest Virtual Meetup?
In this session, we cover some of the biggest updates coming to #VictoriaMetrics, including:
- Added support for vmselect #RPC in vmsingle
- Introduced #Monitoring Data eXchange (MDX)
- Released #vmestimator for real-time cardinality estimation
- Added #Prometheus Native Histogram ingestion
- Improved #vmagent remote write to prioritize recent metrics
Watch it on demand! 🎥
https://www.youtube.com/watch?v=qptvcexoxIc
Anyone else DIY monitor the air quality in their living space with a raspberry Pi and get mobile notifications about status?
Just me?
Starting from a single validation policy, we show how policy evaluations and enforcement results are exposed as metrics, ingested into VictoriaMetrics, and queried through a standard #Prometheus-compatible API. A minimal dashboard is then used to inspect policy failures, affected namespaces, and policy execution duration.
Watch it on Demand
https://bit.ly/3RUcugF
Heads up for those running #Prometheus on #Debian unstable or testing:
prometheus (3.5.3+ds1-1) urgency=medium
The Prometheus Web UI has been completely disabled in this package. Upstream removed the Classic UI in v2.34.0. The newer React and Mantine UIs cannot be shipped because they require complex, pre-compiled toolchains (node-vite and rust-rolldown) that are not yet packaged in Debian and cannot be built offline.
Install `apt-listchanges` and update manually.
Is there anything decent for #Prometheus and #PHP monitoring? All the PHP exporters look to have been abandoned 4 or more years ago. There also seems to be a lack of decent data from #nginx exporters. I guess for PHP, I'd need to use some kind of OpenTelemetry stuff? For nginx it might have to be feeding access logs into something?
🥳 New update - Real-time Cardinality Estimations for #VictoriaMetrics and #Prometheus
#Cardinality problems usually begin with a small, seemingly harmless change: you add a label, and suddenly one metric becomes thousands of unique series.
Starting from a single validation policy, we show how policy evaluations and enforcement results are exposed as metrics, ingested into VictoriaMetrics, and queried through a standard #Prometheus-compatible API. A minimal dashboard is then used to inspect policy failures, affected namespaces, and policy execution duration.
New post: Monitoring our FreeBSD Mastodon instance.
burningboard.net runs as a stack of Bastille jails on FreeBSD, so I watch it from a separate box with Prometheus, Grafana and Loki. The interesting part is the FreeBSD-shaped gaps: no native ZFS metrics, nothing for the Mastodon API or our S3 media bucket. A small textfile collector fills all of it.
This is how I keep an eye on the very instance I'm writing this on:
https://blog.hofstede.it/monitoring-a-freebsd-mastodon-instance-with-prometheus-grafana-and-loki/
May was awesome for the VictoriaMetrics #Observability Stack 🚀
We’ve introduced a range of updates and new features across VictoriaMetrics.
📊 Native #Prometheus histograms support: native histogram ingestion is now supported across vmagent, vmsingle, and cluster.
🛡️ More reliable vmagent shutdown: draining in-memory queues before fallback, reducing alerting gaps.
🔄 Smarter rerouting: improved vminsert handling to avoid rerouting storms and stabilize ingestion.
At a large enough scale, #observability becomes a systems design problem worth studying. In this post, we’ll walk through how Airbnb got there, why aggregation was essential, and how vmagent became the piece that completed the puzzle. 👇
https://bit.ly/4xaJHnG
This talk presents a simple, technical workflow for observing Kubernetes policy behavior using Kyverno and VictoriaMetrics. Starting from a single validation policy, we show how policy evaluations and enforcement results are exposed as metrics, ingested into VictoriaMetrics and queried through a standard #Prometheus-compatible API. A minimal dashboard is then used to inspect policy failures, affected namespaces, and policy execution duration.
📍 The East Hub
🕣 02:35 PM
The Challenge?
- Performance bottlenecks with individual #Prometheus instances hitting CPU and memory ceilings
- #Alerting pipelines where reliability is non-negotiable
- Heavy operational overhead from managing a complex federated architecture
With #VictoriaMetrics, DSV optimized efficiency, scalability, and reliability across their Kubernetes environments.
👉 Learn more in our case study
https://bit.ly/4vmBI5r
Scaling #Kubernetes #observability isn’t just about collecting more metrics. It’s about making them usable at scale.
At Global Transport and Logistics, a global leader in freight and logistics, the team chose #VictoriaMetrics to overcome the limits of their federated #Prometheus setup as their Kubernetes environments rapidly expanded.
Read-only Friday!
Heute schau ich mir mal die Optimierungen für #Grafana Produkte an.
Also #Loki, #Alloy, #Prometheus und #Cortex
Hinsichtlich Memory/CPU usage.
Auf den Satelliten soll diese möglichst gering sein. Darf auch langsam werden dadurch.
Auf dem zentralen System darfs mehr brauchen, wenn's dafür schneller wird.
Mal sehen was Caching bringt!
Also da kannste nichts sagen. Habe 7 Anwendungen von einem #raspberrypi in #Container auf einen #proxmox Server in 1,5 Stunden mit #claudecode umgezogen und konnte nebenher andere Sachen machen. Da waren keine ganz einfachen Sachen dabei. Unter anderem #Grafana / #Prometheus #Datenbank etc.. Das war großes Tennis und eine echte Erleichterung.
👇 Learn why #Spotify Engineering relied on #VictoriaMetrics for extreme #Scale observability in this case study.
https://bit.ly/49e5P6w
#Proxmox #PVE #monitoring #metrics #opensource
https://gyptazy.com/blog/grafana-dashboard-for-pegaprox-prometheus-exporter/