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

Support for OpenTracing #616

Open
screwyprof opened this issue Jul 19, 2022 · 2 comments
Open

Support for OpenTracing #616

screwyprof opened this issue Jul 19, 2022 · 2 comments
Labels
TeamCerberus Under active development by TeamCerberus @Consensys

Comments

@screwyprof
Copy link

It would be great if web3signer could have tracing support.

The important use cases / workflows would be:

  • deposit payload signature request
  • VEM signature request
  • slashing protection triggered

This kind of tracing support will improve visibility of the end-to-end process for key events - these are sensitive processes and if things go wrong, the better our transparency, the quicker we'll be able to resolve

@jframe jframe added the TeamCerberus Under active development by TeamCerberus @Consensys label Jul 20, 2022
@non-fungible-nelson
Copy link
Contributor

@beetrootkid - what do you think the priority of something like this would be?

@beetrootkid
Copy link

@non-fungible-nelson - I do think this is important. (disclosure: @screwyprof is in my team) It will tell us not only about when things go wrong but also help identify where time is being spent. As we ramp up active keys, then this might well become a vital piece of data...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TeamCerberus Under active development by TeamCerberus @Consensys
Projects
None yet
Development

No branches or pull requests

4 participants