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

Adding basic telemetry to the plugin #163

Merged
merged 3 commits into from
Jun 23, 2017
Merged

Conversation

jpricket
Copy link
Contributor

This telemetry will be sent to Application Insights for tracking what features users are engaged with.

- Incoming events from TFS are covered
- Other events like change in status or labeling sources
@jpricket jpricket requested a review from jeffyoung June 23, 2017 15:43
Copy link
Contributor

@jeffyoung jeffyoung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One inline question. Another is: are there any places we'd like to send telemetry when something fails (an exception)? Might be worth considering.

private static final String SYS_PROP_USER_NAME = "user.name";
private static final String SYS_PROP_JAVA_RUNTIME = "java.runtime.name";
private static final String SYS_PROP_JAVA_VERSION = "java.version";
private static final String USER_AGENT_FORMAT = "{0}/{1} {2}/{3} {4}/{5} {6}/{7} ({9})";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do have against 8?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! 9 should be 8.

@jpricket
Copy link
Contributor Author

I agree. There are probably a lot more places we need telemetry. I just wasn't sure where those other places were. This initial telemetry is mostly a guess on the places I think are most interesting. I could be way off. As for error conditions, I just don't know which "catches" are exceptional yet and which aren't :(

Copy link
Contributor

@jeffyoung jeffyoung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks (and sounds) good to me.

@jpricket jpricket merged commit 21f87c0 into master Jun 23, 2017
@jpricket jpricket deleted the users/jpricket/telemetry branch June 23, 2017 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants