Add HTTP telemetry events to Cog startup #1104
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
imbriaco
force-pushed
the
imbriaco/cog-start-telemetry
branch
from
3e869cf to
7474655
Compare
|
Did an in-person review with @kevsmith who gave a 👍 . Merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cog now sends an HTTP event to an Operable telemetry service every time it starts. The message that is sent contains the Cog version number and a unique ID for the Cog instance. Aside from this data, Operable also records the timestamp that the telemetry event was received.
This information is used by Operable in order to help understand the size of the Cog install base and the currently deployed versions. If you would like to opt out of having this telemetry data sent, you can set the
COG_TELEMETRYenvironment variable to the valuefalsebefore starting Cog.