aec6e9d3e8
[chore] Prepare release v1.37.0 ( #2682 )
...
Co-authored-by: otelbot <197425009+otelbot@users.noreply.github.com>
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
2025-08-25 23:15:52 +00:00
4b2c0e6544
[chore] Prepare release v1.36.0 ( #2483 )
2025-07-05 16:48:25 +00:00
a497728679
[chore] Prepare release v1.35.0 ( #2454 )
2025-06-30 19:58:04 +00:00
e96d8de9e8
Prepare release v1.34.0 ( #2285 )
...
Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
2025-05-19 19:44:40 +00:00
9e993af31e
Prepare release v1.33.0 ( #2220 )
...
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
2025-05-02 19:46:16 +00:00
6814d83dac
Prepare release v1.32.0 ( #2039 )
...
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
2025-03-31 08:52:01 -07:00
c01aa89d9a
Prepare release v1.31.0 ( #1970 )
2025-03-10 17:49:47 -07:00
ac424df0d0
Prepare release v1.30.0 ( #1809 )
...
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
2025-01-24 11:04:57 -08:00
0edb9e2b42
Prepare release 1.29.0 ( #1626 )
2024-11-28 10:23:37 -08:00
96f8bda9ba
Prepare release 1.28.0 ( #1458 )
2024-10-07 17:00:55 -07:00
01c542ccac
Prepare release v1.27.0 ( #1307 )
2024-08-02 08:59:05 -07:00
9adff435c7
[chore] Cut 1.26 release. ( #1052 )
2024-05-21 18:20:56 +00:00
f1be1511d9
[chore] Prepare v1.25.0 release ( #878 )
...
Co-authored-by: Joao Grassi <5938087+joaopgrassi@users.noreply.github.com>
2024-04-04 09:45:17 -07:00
cafda71276
Staging the 1.24.0 release ( #613 )
2023-12-15 10:36:02 -08:00
eff3086950
Cherry-pick 1.23.1 schema file (and release notes) to main ( #585 )
...
Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
2023-12-06 09:04:53 -05:00
da1dbb567f
Staging the 1.23.0 release. ( #489 )
...
Co-authored-by: Armin Ruech <7052238+arminru@users.noreply.github.com>
2023-11-03 12:55:57 -04:00
cadfe53949
Stage 1.22.0 release for review. ( #380 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-10-12 09:47:57 -04:00
412a3eff4e
Rename `process.runtime.jvm.cpu.utilization` to `process.runtime.jvm.cpu.recent_utilization` ( #53 )
2023-06-09 10:23:53 -07:00
614dbefc77
BREAKING: Introduce common `url.*` attributes, and improve use of namespacing under `http.*` ( #3355 )
2023-05-08 19:55:53 -07:00
9e3e528ccc
BREAKING: Rename remaining network attributes from `net.*` to `network.*` and align definitions with ECS ( #3426 )
2023-05-08 17:46:55 -07:00
5b8861e8c5
BREAKING: Replace `net.peer.*`/`net.host.*` with `client.*`/`server.*` (and `source.*`/`destination.*`) ( #3402 )
2023-05-08 16:19:51 -07:00
15f3e529f1
BREAKING: Remove `messaging.consumer.id`, make `messaging.client_id` generic ( #3336 )
...
Fixes #2015
## Changes
Based on discussions in the messaging workgroup and in issue #2015 , this
PR proposes to remove `messaging.consumer.id`, and to replace both
`messaging.kafka.client_id` and `messaging.rocketmq.client_id` with a
generic `messaging.client_id`.
`messaging.consumer.id` is defined to always be set to the `client_id`
of the used messaging system, except for Kafka, where it was defined to
be a combination of `messaging.kafka.client_id` and
`messaging.kafka.consumer.group`, or just the latter if
`messaging.kafka.client_id` is not available. With this definition, the
semantics of `consumer.id` are different between messaging systems, and
even different for different Kafka scenarios.
The proposed `messaging.client_id` has consistent semantics ("an unique
client id, when it is available"), and can be used instead of
`messaging.consumer.id` in almost all cases.
In addition to have consistent semantics, this also simplifies the
semantic conventions, as instead of
`messaging.consumer.id`
`messaging.kafka.client_id`
`messaging.rocketmq.client_id`
there is now just:
`messaging.client_id`.
2023-04-24 17:13:21 -06:00
b7e8b54419
BREAKING rename `net.app.protocol.(name|version)` to `net.protocol.(name|version)` and replace `http.flavor` with `net.protocol.(name|version)` ( #3272 )
2023-03-10 10:15:15 -08:00
6d7b233c80
Rename http.user_agent to user_agent.original ( #3190 )
...
Fixes #3180
## Changes
Renames `http.user_agent` to `user_agent.original`.
2023-03-02 14:47:29 -06:00
2447fb063f
Expand scope of `faas.id` to `cloud.resource_id` ( #3188 )
...
## Changes
As per the discussion on #3188 , we determined it is better to move
rather than remove as this attribute is still important for some systems
despite it containing duplicated information.
2023-02-27 12:13:13 -06:00
0d0b9d0a7d
Rename `faas.execution` to `faas.invocation_id` and change units for `faas.max_memory` ( #3209 )
2023-02-20 09:29:24 -06:00
1781e9270e
Add 1.1.8.0 Schema. ( #3175 )
2023-02-07 13:01:58 -06:00
54ca902e06
Update the 1.17 Schema to reference the proper changes PR ( #3099 )
2023-01-12 20:01:16 -06:00
a7ede6fbfa
Refactor messaging attributes and specify per-message attributes ( #2957 )
2022-12-22 17:04:53 -06:00
3f3308305b
Add 1.16.0 Schema. ( #3016 )
2022-12-08 00:37:22 +01:00
34093ed204
Clarify the HTTP client `http.retry_count` spec ( #2743 )
2022-10-18 10:46:16 -07:00
d4943b2d14
Release 1.14.0 ( #2851 )
2022-10-04 23:27:17 +02:00
c01963c823
Revert #2617 , #2675 , #2688 : "add metrics to replace metrics with `direction`" ( #2748 )
...
Please review this carefully. It is not an automatic reverting, I had to fix merge conflicts manually and may have made mistakes, so a thorough review is needed.
Changes:
- This reverts https://github.com/open-telemetry/opentelemetry-specification/pull/2617 . We are reverting it until we are certain how to resolve issue #2726
- Also reverts the corresponding schema file changes done in https://github.com/open-telemetry/opentelemetry-specification/pull/2688
- Also reverts https://github.com/open-telemetry/opentelemetry-specification/pull/2675
~Note that this does not revert https://github.com/open-telemetry/opentelemetry-specification/pull/2675 which I believe to still be valid. If you think otherwise please speak.~ [UPDATE: discussed in Spec SIG and decided to revert 2675 too].
Contributes to https://github.com/open-telemetry/opentelemetry-specification/issues/2726
2022-09-02 10:00:11 -04:00
cceb35c385
Fix 1.12.0 and 1.13.0 schema file ( #2720 )
2022-08-09 17:59:17 -07:00
4ee53745d8
split system.network.connections into TCP and UDP metrics ( #2675 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2022-08-05 17:44:58 +02:00
ec22b65283
Add schema definition for direction change ( #2688 )
...
This is a follow up to https://github.com/open-telemetry/opentelemetry-specification/pull/2617 now that https://github.com/open-telemetry/opentelemetry-specification/pull/2653 has been merged.
2022-07-29 11:42:32 -04:00
216beba6cc
Define net.sock attributes and clarify logical net.peer|host.name attributes ( #2614 )
2022-07-13 10:01:44 -07:00
d967d3e954
Release v1.12.0 ( #2612 )
2022-06-10 09:07:40 -05:00
c2e5407069
Release v1.11.0 ( #2519 )
2022-05-04 17:04:02 -05:00
dcf4580799
Release v1.10.0 ( #2463 )
2022-04-01 09:13:58 -06:00
d88bf5ff7d
Release v1.9.0 ( #2329 )
2022-02-14 09:26:16 -06:00
d42afabd91
Remove db.cassandra.keyspace and db.hbase.namespace, and clarify db.name ( #1973 )
...
Fixes #1760
## Changes
Removes `db.cassandra.keyspace` and `db.hbase.namespace` (in preference for using `db.name`).
Clarifies `db.name` in the case where a database product provides multiple concepts that could be mapped to `db.name`.
2021-10-08 11:58:31 +00:00
830a4223c6
Release v1.7.0 ( #1926 )
2021-09-30 16:23:42 +02:00
74479daa4b
Delete schema 1.6.0 ( #1910 )
...
* Delete 1.6.0
Closes #1909
* Skip schema check for 1.6.0
2021-09-08 22:24:59 -04:00
7c04982127
Add 1.6.1 Schema File ( #1896 )
2021-08-31 14:50:37 +02:00
59717ac29a
Add 1.6.0 Schema File ( #1855 )
...
No schema changes since 1.5.0, so 1.6.0 section is empty in the file.
Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
2021-08-06 18:43:15 +00:00
6b20885222
Add 1.5.0 Schema File ( #1802 )
...
No schema changes since 1.4.0, so 1.5.0 section is empty in the file.
2021-07-07 13:59:51 -04:00
4f77db44df
Add schema file and a script with minimal checks that verifies them ( #1702 )
...
This adds some minimal sanity checks to make sure we don't forget
to add the schema file when we make a release. The checks are tied
to the CHANGELOG.md.
In the future we can do more thorough verifications, e.g. parse the content
of the schema YAML file and ensure it includes the changes that we can
detect by looking at the changes at the semantic convention files.
2021-05-20 10:09:51 -04:00
otelbot[bot]