Earlier quoted context omitted.
This is my setup on all my raspberrypis. I have not be been able to figure out how to monitor a cluster though. I saw that grafana free tier doesn’t allow a cluster of servers getting monitored. I have telegraf + influxdb + grafana installed on all my servers.
Could you expand on what you mean by: > grafana free tier doesn’t allow a cluster of servers getting monitored. Is there a particular aspect of the cluster you're missing? Is it that you don't want individual server metrics?
Systems Monitoring with Prometheus and Grafana
81–90 of 107 posts
Re: Systems Monitoring with Prometheus and Grafana
#82Earlier quoted context omitted.
What do you use as a frontend? As far as I could tell grafana free tier doesn’t allow monitoring cluster of servers.
You could self host it.
Re: Systems Monitoring with Prometheus and Grafana
#83Earlier quoted context omitted.
You could self host it.
Can I self host for monitoring cluster of servers? Currently I have grafana installed on each of my servers and I am having to monitor them individually. I want a centralised dashboard over telegraf + influxdb.
Re: Systems Monitoring with Prometheus and Grafana
#84Earlier quoted context omitted.
Can I self host for monitoring cluster of servers? Currently I have grafana installed on each of my servers and I am having to monitor them individually. I want a centralised dashboard over telegraf + influxdb.
Why would you install Grafana + Influx on each server instead of one central one?
Also I wanted to keep the monitoring unaffected for other servers if one of them go down. If I setup a central server for monitoring then that becomes a single point of failure.
Re: Systems Monitoring with Prometheus and Grafana
#85Re: Systems Monitoring with Prometheus and Grafana
#86Prometheus and Grafana are awesome, use them personally for all my monitoring. However I’m still trying to nail down my high cardinality/highly unique metrics-like data story. What are people using? I’ve heard a combination of Cassandra/BigTable and Spark as a potential solution?
TimescaleDB is a long-term storage option for Prometheus metrics, has no problem with high-cardinality, and now natively supports PromQL (in addition to SQL) [0] (Disclaimer: I work at Timescale) [0] https://github.com/timescale/timescale-prometheus
Re: Systems Monitoring with Prometheus and Grafana
#87What's a good alternative to Prometheus when pulling stats is impractical? Say I want to monitor a personal laptop like I would a server. It will change networks and IP addresses, so pulling would be impractical to configure, whereas the laptop could easily(?) push its stats to a remote server.
I've been using ZeroTier [0] so whenever my laptop is online, it's also accessible by Prometheus so it can be scraped. I run ZeroTier in a container on my router, and on each "road warrior" that needs LAN access (laptop, phone...). The caveat is that I have no metrics when the laptop is offline but that doesn't happen very often anyway. [0] https://www.zerotier.com/
Re: Systems Monitoring with Prometheus and Grafana
#88What's a good alternative to Prometheus when pulling stats is impractical? Say I want to monitor a personal laptop like I would a server. It will change networks and IP addresses, so pulling would be impractical to configure, whereas the laptop could easily(?) push its stats to a remote server.
Prometheus supports writing (replicating) data to a remote endpoint on a per scrape basis with a protocol called remote-write. You can pretty easily set that up on any Prometheus instance. There are quite some implementations to receive those remote-write requests: https://prometheus.io/docs/operating/integrations/#remote-en... You're probably exactly looking for something like that. In fact, I've given a talk about…
Re: Systems Monitoring with Prometheus and Grafana
#89Grafana truly is best in class, but I have strong reservations about Prometheus. I really want to like it, it’s just so _easy_, publish a little webpage with your metrics and Prometheus takes care of the rest. Lovely. But I often find that the cardinality of the data is substantially lower than even the defaults of alternatives (influxdb has 1s and even Zabbix has 5s). Not to mention the lost writes (missing data poi…
My understanding is that Prometheus is designed for you to deploy multiple instances within your company, rather than deploying a limited number of instances for the company or division. So I would reasonably run a Prometheus instance by myself or with my neighboring teams rather than depending on a centralized instance run by $OPS.
Being able to also control which metrics are important to my team vs the wider team is a BIG bonus of this sort of decentralised system.
Re: Systems Monitoring with Prometheus and Grafana
#90I have a love/hate relationship with Prometheus. If I had no budget for metrics its likely the thing I would reach for, but I’m dying for someone to open source a ‘next level’ metrics system (something like Monarch or Circonus but free). But woe betide the team that has to run it as a service. Not that other metrics systems are better but Prometheus can be brutal in that space. As a ‘squad level’ tool its really good…
BTW, I'm working on VictoriaMetrics - open source monitoring solution that works out of the box. See https://github.com/VictoriaMetrics/VictoriaMetrics