You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maintainers aim to periodically release new versions of the packages in `opentelemetry-python-contrib`.
72
+
73
+
Contributions that enhance OTel for Python are welcome to be hosted upstream for the benefit of group collaboration. Maintainers will look for things like good documentation, good unit tests, and in general their own confidence when deciding to release a package with the stability guarantees that are implied with a `1.0` release.
74
+
75
+
To resolve this, members of the community are encouraged to commit to becoming a CODEOWNER for packages in `-contrib` that they feel experienced enough to maintain. CODEOWNERS can then follow the checklist below to release `-contrib` packages as 1.0 stable:
76
+
77
+
### Releasing a package as `1.0` stable
78
+
79
+
To release a package as `1.0` stable, the package:
80
+
- SHOULD have a CODEOWNER. To become one, submit an issue and explain why you meet the responsibilities found in [CODEOWNERS](.github/CODEOWNERS).
81
+
- MUST have unit tests that cover all supported versions of the instrumented library.
82
+
- e.g. Instrumentation packages might use different techniques to instrument different major versions of python packages
83
+
- MUST have clear documentation for non-obvious usages of the package
84
+
- e.g. If an instrumentation package uses flags, a token as context, or parameters that are not typical of the `BaseInstrumentor` class, these are documented
85
+
- After the release of `1.0`, a CODEOWNER may no longer feel like they have the bandwidth to meet the responsibilities of maintaining the package. That's not a problem at all, life happens! However, if that is the case, we ask that the CODEOWNER please raise an issue indicating that they would like to be removed as a CODEOWNER so that they don't get pinged on future PRs. Ultimately, we hope to use that issue to find a new CODEOWNER.
Copy file name to clipboardexpand all lines: instrumentation/opentelemetry-instrumentation-botocore/src/opentelemetry/instrumentation/botocore/__init__.py
Copy file name to clipboardexpand all lines: sdk-extension/opentelemetry-sdk-extension-aws/src/opentelemetry/sdk/extension/aws/trace/propagation/aws_xray_format.py
+9-1
Original file line number
Diff line number
Diff line change
@@ -18,9 +18,17 @@
18
18
19
19
The **AWS X-Ray Propagator** provides a propagator that when used, adds a `trace
20
20
header`_ to outgoing traces that is compatible with the AWS X-Ray backend service.
21
-
This allows the trace context to be propagated when a trace span multiple AWS
21
+
This allows the trace context to be propagated when a trace spans multiple AWS
22
22
services.
23
23
24
+
The same propagator setup is used to extract a context sent by external systems
25
+
so that child span have the correct parent context.
26
+
27
+
**NOTE**: Because the parent context parsed from the ``X-Amzn-Trace-Id`` header
28
+
assumes the context is _not_ sampled by default, users should make sure to add
29
+
``Sampled=1`` to their ``X-Amzn-Trace-Id`` headers so that the child spans are
0 commit comments