mastodon.green is one of the many independent Mastodon servers you can use to participate in the fediverse.
Plant trees while you use Mastodon. A server originally for people in the EU, but now open for anyone in the world

Administered by:

Server stats:

1.2K
active users

#monitoring

8 posts8 participants0 posts today

#Windkraft kann für #Fledermäuse zur tödlichen Gefahr werden. Das gilt besonders in #Südostasien, wo #Artenvielfalt und #Windkraftausbau aufeinandertreffen.

Eine neue #Risikoanalyse kombiniert weltweite Daten, um gefährdete Arten zu identifizieren.
Klare Empfehlung: Südostasien braucht eigene #Monitoring-Programme, um Windkraft naturverträglich auszubauen und gefährdete #Fledermäuse besser zu schützen.

conbio.onlinelibrary.wiley.com

Replied in thread

@pertho The only little drawback compared to epoll is the lack of atomic signal mask setting, so you need a bit more code and a thoughtful structure to handle signals in the same loop. Apart from that, indeed much better than #epoll.

Unfortunately, it's not beter than inotify (for a completely different purpose, #file #monitoring ... kqueue covers them all). With #inotify, you can for example set a #watch by path, while #kqueue requires opened file descriptors. 😞

Is there an on-premise, open source option for a monitoring/telemetry platform comparable* to say New Relic or Dynatrace with an approachable query language?

Is Prometheus+Grafana pretty much it?

Simpler the better, approachable for a casual user (i.e. curious non-technical tenants) would be great.

* Caveats for "comparable" apply!

Anyone have any advice on a OPEN SOURCE systems/network monitoring tool that isn't #Zabbix or #LibreNMS ? I'm already running those two.

#Nagios is still "half payware", and I'm at a point in my life where I don't need to be editing 400 different configuration files, one for each server/router/etc., so that's Right Out.

Ideally, it'd auto-discover hosts on the network, present them to me in a list, and allow me to configure them via a web client.. just like Zabbix and LibreNMS do.

Why do I want a third monitoring solution? I have my reasons.

So, anyone have any recommends? I'd like to be able to graph uptime, network traffic, CPU and RAM usage, etc. and do it in pretty graphs. I'd also like to be able to do it without spending

Thanks in advance.

Nachdem diverse #ki #ai #crawler besonders respektvoll mit den öffentlichen Ressourcen von Open Source Projekten umgehen, habe ich mich dazu entschlossen eben diese auszusperren. Wir hatten in der Vergangenheit crawls, die im #monitoring als #ddos gewertet wurden.

Diverse AS erfreuen sich nun einem dauerhaften 429, einige wenige die es für alle kaputt machen…

Why does the Kotlin ecosystem have such a relaxed view to monitoring coroutine dispatchers?

"Trust me, bro. Coroutines fast," seems to be the attitude. If you've got a cooperative multitasking framework like a Kotlin coroutine dispatcher, you're gonna want to know when there's enough coroutines not playing nice that it affects something you care about, and you're going to want to be able to make a call about whether it's an annoying, important or now problem.