Add opentelemetry.io docs

[austinlparker]

Per open-telemetry/opentelemetry.io#472, we're mirroring the docs content on the website to each SIG. When a release occurs and these docs are updated, please make an issue or PR mirroring them to their appropriate location in the website repo (https://github.com/open-telemetry/opentelemetry.io/tree/main/content/en/docs/cpp).

[codecov]

Codecov Report

Merging #636 (0aeea99) into main (9fa6bd5) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #636      +/-   ##
==========================================
- Coverage   94.49%   94.47%   -0.02%     
==========================================
  Files         197      197              
  Lines        9130     9130              
==========================================
- Hits         8627     8626       -1     
- Misses        503      504       +1     

Impacted Files	Coverage Δ
...include/opentelemetry/sdk/common/circular_buffer.h	97.87% <0.00%> (-2.13%)	⬇️

[lalitb]

nit - we do have logging api/sdk pre-alpha release.

[ThomsonTan]

And I think Metrics should be "Not Yet Implemented".

[lalitb]

API docs: https://opentelemetry-c-api.readthedocs.io/en/latest/index.html
Contrib repo : https://github.com/open-telemetry/opentelemetry-cpp-contrib

[reyang]

@austinlparker would it be okay to put the @open-telemetry/cpp-maintainers as the "CODEOWNER" of this folder https://github.com/open-telemetry/opentelemetry.io/tree/main/content/en/docs/cpp? In this way we don't have to duplicate the contents in this repo.

I can update the OTel C++ release process and put something like "for each release, update the opentelemetry.io docs".

[reyang]

I've submitted a PR open-telemetry/opentelemetry.io#505. Once it is merged, I'll update the release process doc https://github.com/open-telemetry/opentelemetry-cpp/blob/main/RELEASING.md then we can close this PR.

[reyang]

I wish to explore if we could avoid duplicating docs. Mirroring the docs will create problem since we don't have the same CI rule between the OTel C++ and opentelemetry.io repo.

[austinlparker]

I'm trying to avoid mirroring by making this be the authoritative source - my goal is to have a github action that will push these changes to the website each release.

[austinlparker]

Unfortunately this is one of those things where everyone wants to do this slightly differently :|

[reyang]

I'm trying to avoid mirroring by making this be the authoritative source - my goal is to have a github action that will push these changes to the website each release.

This would be great!

[reyang]

@austinlparker I'm closing this PR as a result of #639.
If there is a way to automatically publish doc from this repo to opentelemetry.io (so we can keep all C++ related docs here), please let us know and we're happy to do it.