Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telemetry (community statistics) about MeshCentral. Data would be anonymized, and data sharing could be disabled. #6626

Open
marclaporte opened this issue Dec 26, 2024 · 1 comment

Comments

@marclaporte
Copy link
Collaborator

marclaporte commented Dec 26, 2024

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:

@si458
Copy link
Collaborator

si458 commented Dec 26, 2024

so ive looked into this the is a number of ways we can achieve this

we can go like traefik does, and just POST to a central server with anonymous data like OS version, node version, etc
and then we have to write a backend to store data and show graphs etc
https://github.com/traefik/traefik/blob/master/pkg/collector/collector.go

OR

we could use something like opentelemetry which is a standard for like microservices
and then use something like prometheus and grafana to create graphs etc
https://opentelemetry.io/docs/languages/js/getting-started/nodejs/
https://opentelemetry.io/docs/languages/js/exporters/#usage-with-nodejs

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants