Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Proposal for checking instrumentation/framework versions#19

Merged
gpolaert merged 6 commits into
masterDataDog/dd-trace-java:masterfrom
gpolaert/version-checkerDataDog/dd-trace-java:gpolaert/version-checkerCopy head branch name to clipboard
Jun 27, 2017
Merged

Proposal for checking instrumentation/framework versions#19
gpolaert merged 6 commits into
masterDataDog/dd-trace-java:masterfrom
gpolaert/version-checkerDataDog/dd-trace-java:gpolaert/version-checkerCopy head branch name to clipboard

Conversation

@gpolaert

Copy link
Copy Markdown
Contributor

No description provided.

@gpolaert gpolaert requested a review from tylerbenson June 26, 2017 20:58
@gpolaert

Copy link
Copy Markdown
Contributor Author

@tylerbenson It's working :) but could you give me your feedback. I'm not very confident using static methods

@tylerbenson tylerbenson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this PR would have been nicer if the version checking was separated from the JMS support.

# Instrument Elasticsearch Transport Client
# ==========================================
RULE elasticsearch
RULE opentracing-elasticsearch-client

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Since these names are used in the config to allow customers to disable instrumentation, I think it would be good to document the list of names, or update the documentation to explain how to find the name needed.

@tylerbenson tylerbenson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks like this diff is mostly confusing because of the differences with the branch it was based on. It might be cleaned up with rebasing, but no big deal.

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

Morty Proxy This is a proxified and sanitized view of the page, visit original site.