-
Notifications
You must be signed in to change notification settings - Fork 562
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
Instrumentation needs to include a version. #214
Comments
From the SIG meeting: All instrumentation in this repo MUST share the same version and it needs to match repository version. This will unify this repos approach and avoid confusion of how things are versioned. It will also alleviate needing to track which versions are compatible with version of This also means that a top-level repository version |
I could help out with adding versions to the existing instrumentation packages, if help is still needed on this? |
Added audit to description. Not done yet. |
I noticed some of the missing ones while working on a different issue, took the liberty of creating #412 for the remaining ones |
With #412 merged all instrumentation modules should include version now and this issue has been fully resolved. |
* Add golint to linters and resolve issues. I decided to remove constructors for some of the propagation types because the constructors can be reduced to either using the zero value or a single, non optional member. * Enable gofmt and commit fixes
Tracer
s andMeter
s both take instrumentation versions as an option. All instrumentation in this repo should included that. This will help in debugging and when a Views API is created could be used to disable or unify different versions of the same instrumentation running on the same server.Meter
andTracer
instrumentation version.Instrumentation Punch List
The text was updated successfully, but these errors were encountered: