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
@@ -65,7 +74,7 @@ Open a pull request against the main
65
74
repo.
66
75
67
76
> **Note**
68
-
> It is recommended to run [pre-commit script](precommit.sh) from the root of
77
+
> It is recommended to run [pre-commit script](scripts/precommit.sh) from the root of
69
78
the repo to catch any issues locally.
70
79
71
80
### How to Receive Comments
@@ -137,7 +146,7 @@ OpenTelemetry supports multiple ways to configure the API, SDK and other compone
137
146
- Environment variables
138
147
- Compiling time configurations provided in the source code
139
148
140
-
### Experimental/Unstable features:
149
+
### Experimental/Unstable features
141
150
142
151
Use `otel_unstable` feature flag for implementation of specification with [experimental](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.27.0/specification/document-status.md) status. This approach ensures clear demarcation and safe integration of new or evolving features. Utilize the following structure:
143
152
@@ -147,9 +156,10 @@ Use `otel_unstable` feature flag for implementation of specification with [exper
147
156
// Your feature implementation
148
157
}
149
158
```
159
+
150
160
It's important to regularly review and remove the `otel_unstable` flag from the code once the feature becomes stable. This cleanup process is crucial to maintain the overall code quality and to ensure that stable features are accurately reflected in the main build.
151
161
152
-
### Optional features:
162
+
### Optional features
153
163
154
164
The potential features include:
155
165
@@ -173,38 +183,6 @@ projects in this workspace.
173
183
- Run `cargo bench` - this will run benchmarks to show performance
174
184
regressions
175
185
176
-
## Approvers and Maintainers
177
-
178
-
For GitHub groups see the [code owners](CODEOWNERS) file.
*[`opentelemetry-prometheus`] provides a pipeline and exporter for sending
124
-
metrics information to [`Prometheus`].
125
+
metrics to [`Prometheus`].
125
126
*[`opentelemetry-semantic-conventions`] provides standard names and semantic
126
127
otel conventions.
127
-
*[`opentelemetry-stackdriver`] provides an exporter for Google's [Cloud Trace]
128
-
(which used to be called StackDriver).
129
-
*[`opentelemetry-zipkin`] provides a pipeline and exporter for sending trace
130
-
information to [`Zipkin`].
131
-
132
-
Additionally, there are also several third-party crates which are not
133
-
maintained by the `opentelemetry` project. These include:
134
-
135
-
*[`tracing-opentelemetry`] provides integration for applications instrumented
136
-
using the [`tracing`] API and ecosystem.
137
-
*[`actix-web-opentelemetry`] provides integration for the [`actix-web`] web
138
-
server and ecosystem.
139
-
*[`opentelemetry-application-insights`] provides an unofficial [Azure
140
-
Application Insights] exporter.
141
-
*[`opentelemetry-tide`] provides integration for the [`Tide`] web server and
142
-
ecosystem.
143
-
*[`trillium-opentelemetry`] provides metrics instrumentation for [`trillium`] http servers following [semantic-conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/http-metrics.md).
144
-
145
-
If you're the maintainer of an `opentelemetry` ecosystem crate not listed
146
-
above, please let us know! We'd love to add your project to the list!
0 commit comments