Does anyone know of a tool to monitor #redis pub/sub topics? e.g., messages per second on topics, average message size in bytes, etc.
I know the INFO command gives total stats for all commands, but it'd be nice to have more detail into pub/sub. I'm sure we used to have this at pusher.com, but not sure how, and that was over a decade ago, before they moved to an in-house developed messaging infrastructure
What are y'all using for on-prem service health/ #monitoring? Our #nagios install needs a rebuild, and now is as good a time as any to look at other options.
We have a mixed environment of Windows Server 2012r2, 2022, CentOS 7 and Ubuntu 20.04, if that makes any difference.
another reason i love #uptimekuma is being able to see what went wrong with a request. here you can see that https://cyberfurz.social went down for a few minutes, but recovered. 502 is a bad gateway error, so most likely nothing was wrong with the server software itself, just a faulty network connection down the line. really neat stuff!
Just set up a log watcher via Datadog for my Mastodon server cluster, because it's the most pretty and easiest for me in this situation. Works amazing and now I will receive a notification from even a tiniest anomaly!
Looking to build a simple #python#app on top of my search project for a nicer #UI and eventually doing some #monitoring & #logging of user activity. Haven’t worked on this since uni when we used #flask and sometimes a bit of #django. Anyone have any good insights / best practices / favorite reference for something like this?
Successfully installed netdata on my proxmox homelab host for monitoring. Thought I wouldnt need monitoring with notifications but yesterday I looked at the host stats and the cpu usage spiked a few days ago... Took me a while to figure out but the issue was one vm ran out of disk space because of influxdb...
Now I get a notification via telegram if something is wrong - Nice!
if you want your #instance added, just let me know here on mastodon @taco (reply or dm, whatever)! i'm constantly adding more servers that i find that i want to keep an eye on.
For the 2024 edition of #FOSDEM the #Monitoring and #Observability devroom received 61 submissions, a record high, and the average quality was also quite high.
Building a schedule is a luxury problem... I just sent out the first ten acceptance emails; we have two more slots and will build the schedule with actual times once the reconfirmations come in.
So, die Logitech C615 scheint an #Crowsnest mit #Klipper zu funktionieren. Die Settings sind etwas tricky, weil das mit dem Autofocus nicht so einfach einzustellen ist.
Teams should have a regular review to determine what of their #Observability data is actually being used. Otherwise, "just in case" becomes a value-less justification with uncapped costs.
Over the last few weeks I have been looking for a more advanced self-hosted monitoring system. One that gives me more than just a simple up and down status and one that is config based. I think I found it!
To all you #devops and #sysadmin folks out there - what would you recommend for a centralized #monitoring and #logging solution? I am using a central #syslog-ng service with a #postgresql backend these days. But I am looking for a more sophisticated setup. Preferrably something that can be #selfhosted
If you can point me to some more resources, that would be great. The Internet suggests a whole bunch of different rabbit holes. I want to understand, how companies actually manage their log and monitoring stack without outsourcing to a 3rd party.