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

[Proposal] Use fingerprint instead of 'worker-id' #352

Open
electroape opened this issue May 29, 2021 · 0 comments
Open

[Proposal] Use fingerprint instead of 'worker-id' #352

electroape opened this issue May 29, 2021 · 0 comments

Comments

@electroape
Copy link

Use a fingerprint for server-client communication instead of 'worker-id', the latter will be used only as a display name in dashboard.
Fingerprint is a randomly generated string (say, 16 byte alphanumeric). After startup, the daemon looks up the 'worker-fingerprint' option in the config and if it's not present, generates and writes out a new one. Storing the fingerprint in the config allows for dashboard client statistics data continuity. Don't forget about keeping the fingerprint option intact while applying templates.

Advantages :

  • No merging of multiple clients with the same 'worker-id'

Wanted to do this myself at first but can't figure out how to do a config write-out yet.

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

No branches or pull requests

1 participant