-
Notifications
You must be signed in to change notification settings - Fork 40
feat: rich info for telemetry #723
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
Conversation
b5bd769 to
3bbe531
Compare
peterwht
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
For transparency: I did not do a very detailed review. Each change seemed reasonable and doesn't seem risky.
|
Not sure if you have the time but if it is easy, can you look at #635 for additional things? |
43d9c6e to
45e5e9b
Compare
@Daanvdplas yes, that enhances tests for telemetry. Could be a good addition. |
AlexD10S
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I see some clone() included, but I understand the reason behind it
This PR allows telemetry to have very complete data of all commands being used by serializing as JSON the commands being run, even at the end of the workflow when they have already been populated in case the user did not specify all possible parameters.
Sensitive data has been excluded from this serialization.
Screenshot
Statistics will look like this from now on: