Skip to content

Commit cfe6d5a

Browse files
authored
Merge branch 'main' into pytyped
2 parents 098929a + 9697f80 commit cfe6d5a

File tree

13 files changed

+317
-163
lines changed

13 files changed

+317
-163
lines changed

CHANGELOG.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
99

1010
- Removed superfluous py.typed markers and added them where they were missing
1111
([#4172](https://github.com/open-telemetry/opentelemetry-python/pull/4172))
12+
- Include metric info in encoding exceptions
13+
([#4154](https://github.com/open-telemetry/opentelemetry-python/pull/4154))
14+
- sdk: Add support for log formatting
15+
([#4137](https://github.com/open-telemetry/opentelemetry-python/pull/4166))
1216

1317
## Version 1.27.0/0.48b0 (2024-08-28)
1418

CONTRIBUTING.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -224,6 +224,23 @@ updating the GitHub workflow to reference a PR in the Contrib repo
224224
* Trivial change (typo, cosmetic, doc, etc.) doesn't have to wait for one day.
225225
* Urgent fix can take exception as long as it has been actively communicated.
226226

227+
#### Allow edits from maintainers
228+
229+
Something _very important_ is to allow edits from maintainers when opening a PR. This will
230+
allow maintainers to rebase your PR against `main` which is necessary in order to merge
231+
your PR. You could do it yourself too, but keep in mind that every time another PR gets
232+
merged, your PR will require rebasing. Since only maintainers can merge your PR it is
233+
almost impossible for maintainers to find your PR just when it has been rebased by you so
234+
that it can be merged. Allowing maintainers to edit your PR also allows them to help you
235+
get your PR merged by making any minor fixes to solve any issue that while being unrelated
236+
to your PR, can still happen.
237+
238+
#### Fork from a personal Github account
239+
240+
Right now Github [does not allow](https://github.com/orgs/community/discussions/5634) PRs
241+
to be edited by maintainers if the corresponding repo fork exists in a Github organization.
242+
Please for this repo in a personal Github account instead.
243+
227244
One of the maintainers will merge the PR once it is **ready to merge**.
228245

229246
## Design Choices

docs/examples/logs/README.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ Start the Collector locally to see data being exported. Write the following file
1818
endpoint: 0.0.0.0:4317
1919
2020
exporters:
21-
logging:
22-
loglevel: debug
21+
debug:
22+
verbosity: detailed
2323
2424
processors:
2525
batch:
@@ -29,11 +29,11 @@ Start the Collector locally to see data being exported. Write the following file
2929
logs:
3030
receivers: [otlp]
3131
processors: [batch]
32-
exporters: [logging]
32+
exporters: [debug]
3333
traces:
3434
receivers: [otlp]
3535
processors: [batch]
36-
exporters: [logging]
36+
exporters: [debug]
3737
3838
Then start the Docker container:
3939

docs/examples/logs/otel-collector-config.yaml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ receivers:
55
endpoint: 0.0.0.0:4317
66

77
exporters:
8-
logging:
9-
loglevel: debug
8+
debug:
9+
verbosity: debug
1010

1111
processors:
1212
batch:
@@ -16,8 +16,8 @@ service:
1616
logs:
1717
receivers: [otlp]
1818
processors: [batch]
19-
exporters: [logging]
19+
exporters: [debug]
2020
traces:
2121
receivers: [otlp]
2222
processors: [batch]
23-
exporters: [logging]
23+
exporters: [debug]

docs/examples/metrics/instruments/README.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Start the Collector locally to see data being exported. Write the following file
1313
endpoint: 0.0.0.0:4317
1414
1515
exporters:
16-
logging:
16+
debug:
1717
1818
processors:
1919
batch:
@@ -22,7 +22,7 @@ Start the Collector locally to see data being exported. Write the following file
2222
pipelines:
2323
metrics:
2424
receivers: [otlp]
25-
exporters: [logging]
25+
exporters: [debug]
2626
2727
Then start the Docker container:
2828

docs/examples/metrics/instruments/otel-collector-config.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ receivers:
55
endpoint: 0.0.0.0:4317
66

77
exporters:
8-
logging:
8+
debug:
99

1010
processors:
1111
batch:
@@ -14,4 +14,4 @@ service:
1414
pipelines:
1515
metrics:
1616
receivers: [otlp]
17-
exporters: [logging]
17+
exporters: [debug]

docs/examples/opencensus-exporter-tracer/docker/collector-config.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ receivers:
55
exporters:
66
jaeger_grpc:
77
endpoint: jaeger-all-in-one:14250
8-
logging: {}
8+
debug:
99

1010
processors:
1111
batch:
@@ -15,5 +15,5 @@ service:
1515
pipelines:
1616
traces:
1717
receivers: [opencensus]
18-
exporters: [jaeger_grpc, logging]
18+
exporters: [jaeger_grpc, debug]
1919
processors: [batch, queued_retry]

0 commit comments

Comments
 (0)