| 1 |
# Experimental Features |
| 2 |
|
| 3 |
The `stdoutmetric` exporter contains features that have not yet stabilized in the OpenTelemetry specification. |
| 4 |
These features are added to the `stdoutmetric` exporter prior to stabilization in the specification so that users can start experimenting with them and provide feedback. |
| 5 |
|
| 6 |
These feature may change in backwards incompatible ways as feedback is applied. |
| 7 |
See the [Compatibility and Stability](#compatibility-and-stability) section for more information. |
| 8 |
|
| 9 |
## Features |
| 10 |
|
| 11 |
- [Observability](#observability) |
| 12 |
|
| 13 |
### Observability |
| 14 |
|
| 15 |
The `stdoutmetric` exporter provides an observability feature that allows you to monitor the exporter itself. |
| 16 |
|
| 17 |
To opt-in, set the environment variable `OTEL_GO_X_OBSERVABILITY` to `true`. |
| 18 |
|
| 19 |
When enabled, the exporter will create the following metrics using the global `MeterProvider`: |
| 20 |
|
| 21 |
- `otel.sdk.exporter.metric_data_point.inflight` |
| 22 |
- `otel.sdk.exporter.metric_data_point.exported` |
| 23 |
- `otel.sdk.exporter.operation.duration` |
| 24 |
|
| 25 |
Please see the [Semantic conventions for OpenTelemetry SDK metrics] documentation for more details on these metrics. |
| 26 |
|
| 27 |
[Semantic conventions for OpenTelemetry SDK metrics]: https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/otel/sdk-metrics.md |
| 28 |
|
| 29 |
## Compatibility and Stability |
| 30 |
|
| 31 |
Experimental features do not fall within the scope of the OpenTelemetry Go versioning and stability [policy](../../../../../VERSIONING.md). |
| 32 |
These features may be removed or modified in successive version releases, including patch versions. |
| 33 |
|
| 34 |
When an experimental feature is promoted to a stable feature, a migration path will be included in the changelog entry of the release. |
| 35 |
There is no guarantee that any environment variable feature flags that enabled the experimental feature will be supported by the stable version. |
| 36 |
If they are supported, they may be accompanied with a deprecation notice stating a timeline for the removal of that support. |