Skip to content

Commit

Permalink
Merge branch 'main' into codeboten/env-var-exporters-console
Browse files Browse the repository at this point in the history
  • Loading branch information
Alex Boten authored Nov 7, 2023
2 parents 9a4229c + 7a7b36e commit 896cba9
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 4 deletions.
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,9 @@ release.
- New exporter implementations do not need to support
`OTEL_EXPORTER_OTLP_SPAN_INSECURE` and `OTEL_EXPORTER_OTLP_METRIC_INSECURE`.
([#3719](https://github.com/open-telemetry/opentelemetry-specification/pull/3719))
- Clarify that the configuration options MAY be implemented by the exporter,
the SDK, or a separate component (e.g. environment-based autoconfiguration component).
([#3730](https://github.com/open-telemetry/opentelemetry-specification/pull/3730))

### Compatibility

Expand Down
6 changes: 3 additions & 3 deletions spec-compliance-matrix.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ formats is required. Implementing more than one format is optional.
| Create TracerProvider | | + | + | + | + | + | + | + | + | + | + | + |
| Get a Tracer | | + | + | + | + | + | + | + | + | + | + | + |
| Get a Tracer with schema_url | | + | + | | + | | | + | | + | | |
| Get a Tracer with scope attributes | | | | | | | | + | | | | |
| Get a Tracer with scope attributes | | | | | | | | + | | + | | |
| Associate Tracer with InstrumentationScope | | | | | + | | | + | | | | |
| Safe for concurrent calls | | + | + | + | + | + | + | + | + | + | + | + |
| Shutdown (SDK only required) | | + | + | + | + | + | + | + | + | + | + | + |
Expand Down Expand Up @@ -67,7 +67,7 @@ formats is required. Implementing more than one format is optional.
| Unicode support for keys and string values | | + | + | + | + | + | + | + | + | + | + | + |
| [Span linking](specification/trace/api.md#specifying-links) | Optional | Go | Java | JS | Python | Ruby | Erlang | PHP | Rust | C++ | .NET | Swift |
| Links can be recorded on span creation | | + | + | | + | + | + | + | + | + | + | |
| Links can be recorded after span creation | | | | | | | | | | | | |
| Links can be recorded after span creation | | | | | | | | | | + | | |
| Links order is preserved | | + | + | | + | + | + | + | + | + | + | |
| [Span events](specification/trace/api.md#add-events) | | | | | | | | | | | | |
| AddEvent | | + | + | + | + | + | + | + | + | + | + | + |
Expand Down Expand Up @@ -102,7 +102,7 @@ formats is required. Implementing more than one format is optional.
| It is possible to create any number of `MeterProvider`s. | X | + | + | + | + | | | + | + | + | + | |
| `MeterProvider` provides a way to get a `Meter`. | | + | + | + | + | | | + | + | + | - | |
| `get_meter` accepts name, `version` and `schema_url`. | | + | + | + | + | | | + | + | + | - | |
| `get_meter` accepts `attributes`. | | | | | | | | + | + | | | |
| `get_meter` accepts `attributes`. | | | | | | | | + | + | + | | |
| When an invalid `name` is specified a working `Meter` implementation is returned as a fallback. | | + | + | + | + | | | | + | + | - | |
| The fallback `Meter` `name` property keeps its original invalid value. | X | - | - | + | + | | | | + | - | - | |
| Associate `Meter` with `InstrumentationScope`. | | | + | + | + | | | | + | + | | |
Expand Down
4 changes: 3 additions & 1 deletion specification/protocol/exporter.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,9 @@ This document specifies the configuration options available to the OpenTelemetry

## Configuration Options

The following configuration options MUST be available to configure the OTLP exporter. Each configuration option MUST be overridable by a signal specific option.
The following configuration options MUST be available to configure the OTLP exporter.
The configuration options MAY be implemented directly in the OTLP exporter, in the SDK, or in a separate component (e.g. environment-based autoconfiguration component).
Each configuration option MUST be overridable by a signal specific option.

- **Endpoint (OTLP/HTTP)**: Target URL to which the exporter is going to send spans or metrics. The endpoint MUST be a valid URL with scheme (http or https) and host, MAY contain a port, SHOULD contain a path and MUST NOT contain other parts (such as query string or fragment). A scheme of https indicates a secure connection. When using `OTEL_EXPORTER_OTLP_ENDPOINT`, exporters MUST construct per-signal URLs as [described below](#endpoint-urls-for-otlphttp). The per-signal endpoint configuration options take precedence and can be used to override this behavior (the URL is used as-is for them, without any modifications). See the [OTLP Specification][otlphttp-req] for more details.
- Default: `http://localhost:4318` [1]
Expand Down

0 comments on commit 896cba9

Please sign in to comment.