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

Track concurrent keysigns as a metric #1604

Closed
CharlieMc0 opened this issue Jan 20, 2024 · 2 comments · Fixed by #1954
Closed

Track concurrent keysigns as a metric #1604

CharlieMc0 opened this issue Jan 20, 2024 · 2 comments · Fixed by #1954
Assignees
Labels
monitoring zetaclient Issues related to ZetaClient
Milestone

Comments

@CharlieMc0
Copy link
Member

It would be helpful to track concurent keysigns via telemetry.

@CharlieMc0 CharlieMc0 added the zetaclient Issues related to ZetaClient label Jan 20, 2024
@lumtis lumtis added this to the v14 milestone Feb 26, 2024
@kevinssgh
Copy link
Contributor

@CharlieMc0 I've reviewed the code and I can provide a metric related to the number of active processors. What this means is an outbound transaction that is currently being processed. This will include the keysign and broadcast, Let me know if this is sufficient.

@kevinssgh
Copy link
Contributor

Another solution would be to add a keysign manager to the TSS signer that keeps track of the number of concurrent keysigns. This will require a bit more work but will be more accurate.

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

Successfully merging a pull request may close this issue.

4 participants