Add HTTP instrumentation compliance matrix #571
Conversation
| The following tables show the compliance of HTTP instrumentation published under the OpenTelemetry GitHub org | ||
| with the stable HTTP semantic conventions. | ||
|
|
||
| `+` means the feature is supported, `-` means it is not supported, `N/A` means |
There was a problem hiding this comment.
I don't fully get how that description relates to the Latest 1.x version value in the cells below. Should we describe what a version in the cell means?
| `+` means the feature is supported, `-` means it is not supported, `N/A` means | ||
| the feature is not applicable to the particular instrumentation, blank cell means the | ||
| status of the feature is not known. | ||
|
|
There was a problem hiding this comment.
Should we maybe also describe here or at least link to the definition / meaning of OTEL_SEMCONV_STABILITY_OPT_IN somewhere here?
|
I'm concerned with who will maintain this in the long run. Our compatibility matrix is often outdated since it's probably very easy for SIG maintainers to forget to come and update. Imagine this vast number of instrumentations, some even in contrib which SIG maintainers maybe are not even involved that much. I have the idea that this is probably more useful/easy to maintain if it's close to the instrumentation code/repo. I as a end-user/developer maybe are not even aware of the semconv repo I just know I use library xyz. I go to library xyz for questions. |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
No description provided.