Got one more panel in my Prosody monitoring dashboard. From now on slow Prosody internal actions (>2s) are logged and visualized in the bottom graph.

The peak that you can see in the screenshot was caused by too sensitive trigger values (0.0001s) and a server restart.

Ich drück dir die Daumen, dass es dich hinsichtlich der Ursachenforschung weiterbringt. Btw, welches Dashboard-Tool nutzt du?

@trashserver what is the program doing the monitoring?

Or is it a roll your own?

@smallsees it's a combination of Prosody internal monitoring, Netdata, Prometheus and Grafana :)

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!