-
Notifications
You must be signed in to change notification settings - Fork 825
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
Document latest Metrics SDK #3026
Comments
I believe all docs should be moved to the website. We can iterate on them here and move them to the website when we're happy with them? |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This was discussed a bit at the maintainer's meeting last week. On the docs side, we have outlines that can be followed now! Getting started: open-telemetry/opentelemetry.io#1746 (comment) As mentioned in the call, if y'all can contribute a code sample that handles initialization of metrics in the most correct way, then we (docs SIG) can probably cover the rest iteratively. I also think that JS getting started is unique, since there's really two major SDKs that people use, whereas other languages just have one way to get started. I'd recommend that for now, we focus on the Manual Instrumentation doc and then figure out the right way to structure the JS getting started docs orthogonally. |
Sorry to leave you hanging for so long I promise I haven't forgotten this. I'll make sure to get something tomorrow even if it isn't completely polished so you have something to work with. |
Sounds good! |
We need to update the standalone documents of Metrics SDK to help people understand the metrics spec changes and how JavaScript SDK implements them.
The text was updated successfully, but these errors were encountered: