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
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+2
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,8 @@ Please describe the tests that you ran to verify your changes. Provide instructi
21
21
22
22
# Checklist:
23
23
24
+
See [contributing.md](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/master/CONTRIBUTING.md) for styleguide, changelog guidelines, and more.
25
+
24
26
-[ ] Followed the style guidelines of this project
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-2
Original file line number
Diff line number
Diff line change
@@ -104,12 +104,13 @@ A PR is considered to be **ready to merge** when:
104
104
reasonable time to review.
105
105
* Trivial change (typo, cosmetic, doc, etc.) doesn't have to wait for one day.
106
106
* Urgent fix can take exception as long as it has been actively communicated.
107
+
* A changelog entry is added to the corresponding changelog for the code base, if there is any impact on behavior. e.g. doc entries are not required, but small bug entries are.
107
108
108
109
Any Approver / Maintainer can merge the PR once it is **ready to merge**.
109
110
110
111
## Design Choices
111
112
112
-
As with other OpenTelemetry clients, opentelemetry-python follows the
113
+
As with other OpenTelemetry clients, opentelemetry-python follows the
It's especially valuable to read through the [library guidelines](https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/library-guidelines.md).
@@ -122,7 +123,7 @@ use cases are clear, but the method to satisfy those uses cases are not.
122
123
As such, contributions should provide functionality and behavior that
123
124
conforms to the specification, but the interface and structure is flexible.
124
125
125
-
It is preferable to have contributions follow the idioms of the language
126
+
It is preferable to have contributions follow the idioms of the language
126
127
rather than conform to specific API names or argument patterns in the spec.
127
128
128
129
For a deeper discussion, see: https://github.com/open-telemetry/opentelemetry-specification/issues/165
Copy file name to clipboardExpand all lines: instrumentation/opentelemetry-instrumentation-botocore/src/opentelemetry/instrumentation/botocore/__init__.py
+19-6
Original file line number
Diff line number
Diff line change
@@ -27,17 +27,12 @@
27
27
28
28
.. code:: python
29
29
30
-
from opentelemetry import trace
31
30
from opentelemetry.instrumentation.botocore import BotocoreInstrumentor
32
-
from opentelemetry.sdk.trace import TracerProvider
33
31
import botocore
34
32
35
-
trace.set_tracer_provider(TracerProvider())
36
33
37
34
# Instrument Botocore
38
-
BotocoreInstrumentor().instrument(
39
-
tracer_provider=trace.get_tracer_provider()
40
-
)
35
+
BotocoreInstrumentor().instrument()
41
36
42
37
# This will create a span with Botocore-specific attributes
0 commit comments