-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Use of outdated collector API version in documentation #2090
Comments
In general I think the docs should use only the latest APIs. Right now the collector is still (technically) pre-release, and so we can expect any number of further breaking changes to the API until such a time that it's considered stable. Since those older APIs won't be supported, it's not worth documenting how to use them. |
where do you see use of 0.53 collector? We try to auto-update the collector versions on release, so if the version is hardcoded somewhere we should fix that. |
I was following the tutorial for creating a trace receiver and I discovered a disparity between the collector API used and the most recent one the hyperlinks to the source code also points to v0.53: I have however implemented the trace receiver tutorial with v0.66 of the colector API |
thanks, we will need to take the collector version variable we have in the getting started and use it in that page as well |
We should avoid duplicating version info. I've updated the following umbrella issue with proposed solutions: |
Agreed. |
I'm going to close this since the problems reported here will be addressed (in part) and/or tracked elsewhere:
If you think that something isn't covered by the items above, comment here. |
I can see the documentation is based on version 0.53 of the collector API. I have opened this issue to discuss if the documentation should just reflect the latest version of collector API or better still there should be documentation for every collector release.
The text was updated successfully, but these errors were encountered: