@vinishor well... #GoToSocial exposes #prometheus metrics. My VMAgent scraps those and store them in #VictoriaMetrics.

Long story here: https://www.tumfatig.net/2025/monitoring-gotosocial-using-collectd-and-victoriametrics/

Managed #Prometheus vs #VictoriaMetrics #Cloud = 1.5–5X cost saving. Deploying a single deployment with VictoriaMetrics #Cloud can bring massive savings when compared with Managed Prometheus service offerings:

The comparison doesn’t take into account querying to avoid complexity, but keep in mind that in VictoriaMetrics Cloud: querying is included.

Create a deployment (30-day free trial) and see the new pricing for yourself: https://bit.ly/3YSJzJJ

On installe munin et munin-node et tada, on a plein d'infos pour monitorer son serveur debian ou ubuntu.

Vazy faire aussi simple avec #prometheus et #grafana, c'est moi ou c'est ultra relou d'obtenir autant d'infos qu'avec #munin ?

🟣 Integrate smoothly into existing #Prometheus / Grafana / #OpenTelemetry based monitoring stacks, combining VictoriaMetrics’ compatibility and interoperability with CloudRaft’s hands-on observability consulting experience.

We’re looking forward to working closely with the CloudRaft team to reduce infrastructure cost and complexity for enterprises, while delivering fast, simple, reliable and efficient #observability at any scale.

#StrategicPartnership

The latest VictoriaMetrics releases introduce major enhancements across several of its core components, including vmagent, #vmalert, vmctl, and their toolset.
New in v1.130.0:
✨ Metric metadata support (#Prometheus-compatible API)
#VictoriaMetrics can now scrape and store metadata using vmsingle or vmagent and expose it via /api/v1/metadata. Enable it with -enableMetadata=true across vmsingle, vmagent, and vminsert.

VictoriaMetrics #Kubernetes Operator, #VictoriaLogs, and #VictoriaTraces have new features:
🚀 The operator now supports VictoriaLogs and VictoriaTraces in both Single Node and Cluster-based versions — a very significant release.
🔄Better #Prometheus-Operator Compatibility
scrapeClass & scrapeClassName support across VM*Scrape objects

Find more information in our latest blog post 👇
https://bit.ly/4a5hDZX

#Traces #Monitoring #Observability #Logs

This #partnership brings together Allenta's consultative strength with VictoriaMetrics' powerful time-series platform, giving Spanish enterprises a clear path to:
🟣 Scalable #observability that grows with their business
🟣 Dramatic reductions in storage costs and resource consumption
🟣 Seamless #Prometheus compatibility for easy adoption
🟣 Expert implementation and support from a proven local partner
We're looking forward to building something together with the Allenta team.
#SRE #devops

@brendangregg how expensive would be having these traces enabled all the time? https://github.com/brendangregg/perf-tools/blob/master/fs/cachestat or how much sense would it make to monitor that for very long periods, as in on a #prometheus?

#Linux #Monitoring

Together, we’ll help more customers in Benelux and Sweden:
🟣 Handle millions of samples per second with ease.
🟣 Benefit from up to 10x better data compression compared to many legacy solutions.
🟣 Cover any complexity, from simple single-node setups to large, distributed clusters.
🟣 Integrate thanks to #Prometheus compatibility and support for many popular #monitoring solutions as a remote storage or data source.

While this usually works great, recording rules have a cost: The raw metrics still need to be stored in the #Prometheus, even if we don't need them Recording rule need to be executed on interval basis, putting extra pressure on the Prometheus Adding a recording rule always means storing&processing more data.
Save the date today! 👇
https://osoday.com

#Observability #Monitoring

🟣 #VictoriaMetrics will say present as OPEN SOURCE OBSERVABILITY DAY 2025 - October 23-24: one of our co-founders, Roman Khavronenko will present “Aggregating Metrics In-Flight: Challenges and Opportunities”. One of the common practices for improving the query speed in #Prometheus is to create recording rules for commonly used queries.

Recording rules need to be executed on an interval basis, putting extra pressure on the #Prometheus Adding a recording rule always means storing and processing more data. Watch the talk On-Demand 👇
https://bit.ly/4owPKhi

#SRE Day in London was great!
One of our co-founders, Roman Khavronenko presented “Aggregating Metrics In-Flight: Challenges and Opportunities”. One of the common practices for improving the query speed in #Prometheus is to create recording rules for commonly used queries. While this usually works great, recording rules have a cost: The raw metrics still need to be stored in #Prometheus, even if we don't need them.

PromCon 2025 kicks off tomorrow, the biggest conference for #Prometheus fans! 🎉

Come visit us at the #Google Offices in Munich, Germany 🇩🇪 on October 21–22, 2025. We're excited to catch up with the community, share our latest innovations, and chat all about #OpenSource #monitoring and observability.

Looking forward to seeing you there!🎉
https://bit.ly/4mTZ4Lo

#TechEvents #Observability #MonitoringSolutions #Promcon

Does anyone use process_exporter (either stand alone, or via #Grafana #Alloy)?

If so are you monitoring all processes or specific? At work they want to monitor all processes on every server but this is making a cardinality nightmare.

#prometheus #devops #monitoring

Switching to #VictoriaMetrics transformed their approach:
✨ 80% less memory than #Prometheus
✨ Handles 76M+ active time series effortlessly
✨ Ingests 450K+ data points/sec in production
✨ Boosts visibility & customer experience
Learn how they did it — read the full case study! 👇
https://bit.ly/4798zQx

#Observability #TimeSeries #CaseStudy

But at least,

it didn't ask me for diner...

Just noticed after preparing my #mimir #prometheus multi cluster setup over the last days that there is no #kubernetes native or gitops friendly way to upload alerting rules to the mimir ruler (besides Alloy but well) fml

#selfhosting #monitoring