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
How would this be useful? To know what features are used and help us decide when we can remove legacy code. Ex.: We added support for Bootstrap themes: #6333 and I wrote in the issue: "In a few years, when almost everyone is using the Bootstrap themes, for a major version, we can remove non-Bootstrap themes (We will rediscuss this as a community in a few years)". How will we know the time is right? If we had telemetry, and the data showed that 96% of the community is using Bootstrap, it will be easy to justify removing the legacy code.
one other good thing is IF we used say the promethus exporter from opentelemetry,
we can kill 2 birds with 1 stone, by submitting annoymous stats to ourselves
BUT also offer a prometheus /metrics endpoint on your meshcentral server
this will then allow admins of meshcentral server to use there own prometheus instance
to monitor meshcentral like number of amt devices, connected device count, etc!
It would be interesting to have more data about how MeshCentral is used. This was discussed at the December 2024 community meeting: https://github.com/Ylianst/MeshCentral/wiki/Community-Monthly-Meetings. Recording will be here: https://videos.evoludata.com/
How would this be useful? To know what features are used and help us decide when we can remove legacy code. Ex.: We added support for Bootstrap themes: #6333 and I wrote in the issue: "In a few years, when almost everyone is using the Bootstrap themes, for a major version, we can remove non-Bootstrap themes (We will rediscuss this as a community in a few years)". How will we know the time is right? If we had telemetry, and the data showed that 96% of the community is using Bootstrap, it will be easy to justify removing the legacy code.
Related links:
Other Open Source projects doing telemetry:
The text was updated successfully, but these errors were encountered: