feat: Adds telemetry events to submitter and adaptor #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the problem/requirement? (What/Why)
We can't currently tell if anyone is using KeyShot submitters / adaptors
What was the solution? (How)
Uses changes from aws-deadline/deadline-cloud#205 to capture more package information when sending telemetry data, and changes from aws-deadline/deadline-cloud#212 to opt out of telemetry from an environment variable.
What is the impact of this change?
We can better tell how customers use our software and if they use KeyShot
How was this change tested?
Was this change documented?
Updated README with opt out instructions
Is this a breaking change?
No