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
Your pull request should be named according to the
82
+
[conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) standard. This ensures that
83
+
when the PR is squashed into `main`, the resulting commit message is consistent and makes it easier
84
+
for us to generate a changelog standard.
85
+
81
86
> **Note**
82
-
> It is recommended to run [pre-commit script](scripts/precommit.sh) from the root of
83
-
the repo to catch any issues locally.
87
+
> It is recommended to run [pre-commit script](scripts/precommit.sh) to catch any issues locally.
84
88
85
89
### How to Receive Comments
86
90
@@ -140,7 +144,7 @@ For a deeper discussion, see:
140
144
141
145
Currently, the Opentelemetry Rust SDK has two ways to handle errors. In the situation where errors are not allowed to return. One should call global error handler to process the errors. Otherwise, one should return the errors.
142
146
143
-
The Opentelemetry Rust SDK comes with an error type `opentelemetry::Error`. For different function, one error has been defined. All error returned by trace module MUST be wrapped in `opentelemetry::trace::TraceError`. All errors returned by metrics module MUST be wrapped in `opentelemetry::metrics::MetricsError`. All errors returned by logs module MUST be wrapped in `opentelemetry::logs::LogsError`.
147
+
The Opentelemetry Rust SDK comes with an error type `opentelemetry::Error`. For different function, one error has been defined. All error returned by trace module MUST be wrapped in `opentelemetry::trace::TraceError`. All errors returned by metrics module MUST be wrapped in `opentelemetry::metrics::MetricError`. All errors returned by logs module MUST be wrapped in `opentelemetry::logs::LogsError`.
144
148
145
149
For users that want to implement their own exporters. It's RECOMMENDED to wrap all errors from the exporter into a crate-level error type, and implement `ExporterError` trait.
146
150
@@ -169,7 +173,7 @@ It's important to regularly review and remove the `otel_unstable` flag from the
169
173
The potential features include:
170
174
171
175
- Stable and non-experimental features that compliant to specification, and have a feature flag to minimize compilation size. Example: feature flags for signals (like `logs`, `traces`, `metrics`) and runtimes (`rt-tokio`, `rt-tokio-current-thread`, `rt-async-std`).
172
-
- Stable and non-experimental features, although not part of the specification, are crucial for enhancing the tracing/log crate's functionality or boosting performance. These features are also subject to discussion and approval by the OpenTelemetry Rust Maintainers. An example of such a feature is `logs_level_enabled`.
176
+
- Stable and non-experimental features, although not part of the specification, are crucial for enhancing the tracing/log crate's functionality or boosting performance. These features are also subject to discussion and approval by the OpenTelemetry Rust Maintainers.
173
177
174
178
All such features should adhere to naming convention `<signal>_<feature_name>`
0 commit comments