You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For me a short remindert, i am a main developer of the more or less well supported monitoring tool yanic.
After the time, i have seen a lot of code supposed to monitoring in a mesh network, which all are very small single point of code usage.
In the world of cloud, i see that the tools become more easier and standarize e.g. Prometheus.
So i have this Idea / Suggestion for an easy monitoring setup:
respondd only announce nodeinfo (so an monitoring-solution could discovery nodes)
the gluon "status-page" get an permanent metric endpoint (ala https://openmetrics.io/ / Prometheus)
that could be used by the status page, Prometheus of course, but also other systems like influxdb
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
For me a short remindert, i am a main developer of the more or less well supported monitoring tool yanic.
After the time, i have seen a lot of code supposed to monitoring in a mesh network, which all are very small single point of code usage.
In the world of cloud, i see that the tools become more easier and standarize e.g. Prometheus.
So i have this Idea / Suggestion for an easy monitoring setup:
I believe that would create more synergy between normal hosting/monitoring and freifunk/gluon.
Beta Was this translation helpful? Give feedback.
All reactions