Skip to content

Commit

Permalink
Merge branch 'main' into histogram_bucket
Browse files Browse the repository at this point in the history
  • Loading branch information
dashpole authored Jan 20, 2023
2 parents 124c7f9 + 025f8fc commit 54857dc
Show file tree
Hide file tree
Showing 11 changed files with 254 additions and 155 deletions.
106 changes: 78 additions & 28 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,36 +7,108 @@ release.

## Unreleased

- Remove spaces from example exporter User-Agent header to conform to RFC7231 & RFC7230.
[#3052](https://github.com/open-telemetry/opentelemetry-specification/pull/3052)
### Context

### Traces

### Metrics

### Logs

### Resource

### Semantic Conventions

### Compatibility

### OpenTelemetry Protocol

### SDK Configuration

### Telemetry Schemas

### Common

## v1.17.0 (2023-01-17)

### Context

- No changes.

### Traces

- Clarify that the BatchSpanProcessor should export batches when the queue reaches the batch size
([#3024](https://github.com/open-telemetry/opentelemetry-specification/pull/3024))
- Deprecate jaeger exporter, scheduled for spec removal in July 2023.
[#2858](https://github.com/open-telemetry/opentelemetry-specification/pull/2858)

### Metrics

- Rename built-in ExemplarFilters to AlwaysOn, AlwaysOff and TraceBased.
([#2919](https://github.com/open-telemetry/opentelemetry-specification/pull/2919))
- Add `MaxScale` config option to Exponential Bucket Histogram Aggregation.
([#3017](https://github.com/open-telemetry/opentelemetry-specification/pull/3017))
- Rename exponential bucket histogram aggregation to base 2 exponential histogram
aggregation. Rename "OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION"
value from "exponential_bucket_histogram" to
"base2_exponential_bucket_histogram". Mark exponential histogram data model and
base2 exponential histogram aggregation as stable.
([#3041](https://github.com/open-telemetry/opentelemetry-specification/pull/3041))

### Logs

- Clarify usage of log body for structured logs
([#3023](https://github.com/open-telemetry/opentelemetry-specification/pull/3023))

### Resource

- No changes.

### Semantic Conventions

- Clarify common HTTP attributes apply to both clients and servers
([#3044](https://github.com/open-telemetry/opentelemetry-specification/pull/3044))
- Add `code.lineno` source code attribute
([#3029](https://github.com/open-telemetry/opentelemetry-specification/pull/3029))
- Add ClickHouse to db.system semantic conventions
([#3011](https://github.com/open-telemetry/opentelemetry-specification/pull/3011))
- Refactor messaging attributes and per-message attributes in batching scenarios.
([#2957](https://github.com/open-telemetry/opentelemetry-specification/pull/2957)).
BREAKING: rename `messaging.consumer_id` to `messaging.consumer.id`,
`messaging.destination` to `messaging.destination.name`,
`messaging.temp_destination` to `messaging.destination.temporary`,
`messaging.destination_kind` to `messaging.destination.kind`,
`messaging.message_id` to `messaging.message.id`,
`messaging.protocol` to `net.app.protocol.name`,
`messaging.protocol_version`, `net.app.protocol.version`,
`messaging.conversation_id` to `messaging.message.conversation_id`,
`messaging.message_payload_size_bytes` to `messaging.message.payload_size_bytes`,
`messaging.message_payload_compressed_size_bytes` to `messaging.message.payload_compressed_size_bytes`,
`messaging.rabbitmq.routing_key`: `messaging.rabbitmq.destination.routing_key`,
`messaging.kafka.message_key` to `messaging.kafka.message.key`,
`messaging.kafka.consumer_group` to `messaging.kafka.consumer.group`,
`messaging.kafka.partition` to `messaging.kafka.destination.partition`,
`messaging.kafka.tombstone` to `messaging.kafka.message.tombstone`,
`messaging.rocketmq.message_type` to `messaging.rocketmq.message.type`,
`messaging.rocketmq.message_tag` to `messaging.rocketmq.message.tag`,
`messaging.rocketmq.message_keys` to `messaging.rocketmq.message.keys`;
Removed `messaging.url`;
Renamed `send` operation to `publish`;
Split `destination` and `source` namespaces and clarify per-message attributes in batching scenarios.

### Compatibility

- Add Tracer.Close() to the OpenTracing Shim layer.
- Add OpenCensus migration guide and add BinaryPropagation as an option to gRPC
instrumentation for OpenCensus compatibility
([#3015](https://github.com/open-telemetry/opentelemetry-specification/pull/3015)).

### OpenTelemetry Protocol

- Add table for OTLP/HTTP response code and client retry recommendation
([#3028](https://github.com/open-telemetry/opentelemetry-specification/pull/3028))
- Remove spaces from example exporter User-Agent header to conform to RFC7231 & RFC7230.
[#3052](https://github.com/open-telemetry/opentelemetry-specification/pull/3052)

### SDK Configuration

Expand All @@ -46,8 +118,12 @@ release.

### Telemetry Schemas

- No changes.

### Common

- No changes.

## v1.16.0 (2022-12-08)

### Context
Expand Down Expand Up @@ -81,8 +157,6 @@ release.
([#2969](https://github.com/open-telemetry/opentelemetry-specification/pull/2969))
- Make sure it is very clear we are not building a Logging API.
([#2966](https://github.com/open-telemetry/opentelemetry-specification/pull/2966))
- Clarify usage of log body for structured logs
([#3023](https://github.com/open-telemetry/opentelemetry-specification/pull/3023))

### Resource

Expand All @@ -108,8 +182,6 @@ release.
([#2982](https://github.com/open-telemetry/opentelemetry-specification/pull/2982))
- Update hardware metrics to use `direction` as per general semantic conventions
([#2942](https://github.com/open-telemetry/opentelemetry-specification/pull/2942))
- Add ClickHouse to db.system semantic conventions
([#3011](https://github.com/open-telemetry/opentelemetry-specification/pull/3011))

### Compatibility

Expand Down Expand Up @@ -143,28 +215,6 @@ release.

- Rename `http.retry_count` to `http.resend_count` and clarify its meaning.
([#2743](https://github.com/open-telemetry/opentelemetry-specification/pull/2743))
- BREAKING: rename `messaging.consumer_id` to `messaging.consumer.id`,
`messaging.destination` to `messaging.destination.name`,
`messaging.temp_destination` to `messaging.destination.temporary`,
`messaging.destination_kind` to `messaging.destination.kind`,
`messaging.message_id` to `messaging.message.id`,
`messaging.protocol` to `net.app.protocol.name`,
`messaging.protocol_version`, `net.app.protocol.version`,
`messaging.conversation_id` to `messaging.message.conversation_id`,
`messaging.message_payload_size_bytes` to `messaging.message.payload_size_bytes`,
`messaging.message_payload_compressed_size_bytes` to `messaging.message.payload_compressed_size_bytes`,
`messaging.rabbitmq.routing_key`: `messaging.rabbitmq.destination.routing_key`,
`messaging.kafka.message_key` to `messaging.kafka.message.key`,
`messaging.kafka.consumer_group` to `messaging.kafka.consumer.group`,
`messaging.kafka.partition` to `messaging.kafka.destination.partition`,
`messaging.kafka.tombstone` to `messaging.kafka.message.tombstone`,
`messaging.rocketmq.message_type` to `messaging.rocketmq.message.type`,
`messaging.rocketmq.message_tag` to `messaging.rocketmq.message.tag`,
`messaging.rocketmq.message_keys` to `messaging.rocketmq.message.keys`;
Removed `messaging.url`;
Renamed `send` operation to `publish`;
Split `destination` and `source` namespaces and clarify per-message attributes in batching scenarios.
([#2763](https://github.com/open-telemetry/opentelemetry-specification/pull/2763)).

### Metrics

Expand Down
2 changes: 1 addition & 1 deletion schemas/1.17.0
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ versions:
1.17.0:
spans:
changes:
# https://github.com/open-telemetry/opentelemetry-specification/pull/2763
# https://github.com/open-telemetry/opentelemetry-specification/pull/2957
- rename_attributes:
attribute_map:
messaging.consumer_id: messaging.consumer.id
Expand Down
8 changes: 4 additions & 4 deletions spec-compliance-matrix.md
Original file line number Diff line number Diff line change
Expand Up @@ -177,10 +177,10 @@ formats is required. Implementing more than one format is optional.
| The `Sum` aggregation performs as specified. | | + | + | + | + | | | + | | + | + | |
| The `LastValue` aggregation is available. | | + | + | + | + | | | + | | + | + | |
| The `LastValue` aggregation performs as specified. | | + | + | + | + | | | + | | + | + | |
| The `Histogram` aggregation is available. | | + | + | + | + | | | | | + | + | |
| The `Histogram` aggregation performs as specified. | | + | + | | + | | | | | + | + | |
| The explicit bucket `Histogram` aggregation is available. | | - | + | + | + | | | + | | + | + | |
| The explicit bucket `Histogram` aggregation performs as specified. | | - | + | + | + | | | + | | + | + | |
| The `ExplicitBucketHistogram` aggregation is available. | | - | + | + | + | | | + | | + | + | |
| The `ExplicitBucketHistogram` aggregation performs as specified. | | - | + | + | + | | | + | | + | + | |
| The `ExponentialBucketHistogram` aggregation is available. | | | | | | | | | | | | |
| The `ExponentialBucketHistogram` aggregation performs as specified. | | | | | | | | | | | | |
| The metrics Reader implementation supports registering metric Exporters | | | + | + | + | | | + | | + | + | |
| The metrics Reader implementation supports configuring the default aggregation on the basis of instrument kind. | | | + | | + | | | | | - | - | |
| The metrics Reader implementation supports configuring the default temporality on the basis of instrument kind. | | | + | + | + | | | | | + | | |
Expand Down
Loading

0 comments on commit 54857dc

Please sign in to comment.