80e42491fe
BREAKING: Change span statuses for gRPC server spans ( #3333 )
...
Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/3110
## Changes
The idea behind the PR is to make the spam statuses gRPC convention
similar to HTTP semantic conventions.
The gRPC statuses -> HTTP status codes mapping is not anywhere strictly
defined.
However, there is are some approximations which can be found:
-
bb04e070b3 (diff-c94ff143c8f378e6925a985fa18528a8254a6d7fc34bc855e1de13f1e7f3e464)https://github.com/googleapis/googleapis/blob/master/google/rpc/code.proto
I got confused if we should treat `INTERNAL` as `Error` for
`SpanKind.SERVER` because of:
-
https://github.com/grpc/grpc/blob/master/doc/http-grpc-status-mapping.md
-
a02aae6168/internal/transport/handler_server.go (L90C8-L92)a02aae6168/internal/transport/http_util.go (L73)https://github.com/grpc/grpc/blob/master/doc/statuscodes.md )
of `INTERNAL` says:
> Internal errors. This means that some invariants expected by the
underlying system have been broken. This error code is reserved for
serious errors.
Therefore, I decided to leave it as `Error`. Also because this is
backwards compatible (at least for this gRPC status).
---------
Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
2023-04-03 11:27:56 -06:00
64846c4035
Fix units in the Kafka metric semantic conventions ( #3300 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-03-29 19:16:47 +02:00
e857d8146d
Cosmos DB attributes: fixes UserAgent description ( #3338 )
2023-03-29 09:44:40 -07:00
dcc954abd6
AWS Lambda - remove references to messaging.destination.kind and messaging.source.kind ( #3348 )
2023-03-28 18:14:27 +02:00
b3414fcb7f
Issue #3236 Update attribute requirement levels in hardware metrics semconv ( #3258 )
...
Fixes #3236
## Changes
* Update attributes requirement levels in
`specification\metrics\semantic_conventions\hardware-metrics.md`
* Minor wording corrections
2023-03-24 19:29:20 -05:00
13e82eae88
erlang/elixir: add stacktrace representation to table ( #3313 )
...
Adds the functions to use for stacktrace representation in Erlang/Elixir
to the semantic conventions table for exceptions.
2023-03-24 12:05:38 -06:00
efa4181f83
Added AWS S3 semantic conventions ( #3251 )
2023-03-22 08:29:16 -07:00
006e3b4091
Add Cosmosdb attributes for open telemetry ( #3097 )
2023-03-21 10:49:17 -07:00
139842c9e0
BREAKING: remove messaging.destination.kind and messaging.source.kind values ( #3214 )
...
Fixes #3170 , #3265 , #3249
## Changes
~~We currently allow `topic` or `queue` on `messaging.destination.kind`.
While it's common in messaging world to have one or another, messaging
semantic conventions can be applied to AMPQ communication (which does
not have topic/queue terminology), [socket.io](https://socket.io/ ), and
potentially other less traditional messaging use-cases.~~
It's unclear how `messaging.destination.kind` and
`messaging.source.kind` could be used. The distinction between queue and
topic is significant for messaging and distributed systems, but not for
tracing.
In either case, tracing backends should expect to process traces from 0+
messaging and 0+ messaging consumers. In either case, message consumers
can be simultaneous or consequent and there could be many of them.
The only known case (Solace) where it could be useful is when messaging
system allows having queues and topic with the same name on the same
broker, and it could be used to distinguish one from another.
Based on messaging SIG discussion, the attributes are removed for the
time being until we understand if and how they are useful.
Depending on messaging system queues or topics behavior vary a lot and
in future it would makes more sense to represent actual behavior with
individual attributes such as:
- auto-settlement (at-most-once or at least once guarantees)
- settlement for individual messages or offsets
- broadcast or unicast
- etc
2023-03-21 10:51:55 -06:00
1bae921042
Add `toc` for metric http semconv ( #3318 )
...
## Changes
Add `toc` for metric http semconv markdown file
Signed-off-by: Peter Liu <lpfvip2008@gmail.com>
Co-authored-by: Reiley Yang <reyang@microsoft.com>
2023-03-16 22:52:38 -04: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
ade0ab600a
[editorial] Use path, not external URL, for link to spec page; and fix broken link ( #3310 )
2023-03-10 07:39:32 -08:00
12328be1c2
Metric units should use UCUM case sensitive variant ( #3306 )
2023-03-08 10:57:55 -08:00
d28c963926
Fix grammatical number of metric semconv units ( #3298 )
2023-03-08 09:17:29 -08:00
40a91717ba
Show relationship between http target and route in example usage ( #3292 )
...
## Changes
Clarify relationship between `http.target` and `http.route` by using the
same pattern in the example usage. Having different patterns for the
attribute values distorts the relationship between the two attributes.
A similar pattern is seen in the docs for
[`aws-lambda.md`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/instrumentation/aws-lambda.md#api-gateway-request-proxy-lambda-tracing-passive ),
where `http.target` is `/pets/10` and `http.route` is `/pets/{petId}`.
It's a minor adjustment but should help provide clarity for new users.
---------
Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>
2023-03-08 09:12:28 -08:00
489fea52c8
net.peer.name clarification for HTTP client semconv ( #3276 )
...
Fixes #3273
## Changes
Clarifies that if an HTTP client request is explicitly made to an IP
address, e.g. `http://x.x.x.x:8080 `, then
`net.peer.name` SHOULD be the IP address `x.x.x.x`.
2023-03-06 09:33:35 -06:00
c7c60cae12
Expand pool.name in semantic conventions ( #3050 )
...
according to the discussion here:
https://github.com/open-telemetry/opentelemetry-specification/issues/3038
I'm updating the `pool.name attribute`
2023-03-03 10:59:56 -06:00
c9ff781e94
Make net.sock.host.port conditionally required ( #3246 )
2023-03-02 14:01:52 -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
47cabcf799
Rename Optional attribute requirement level to Opt-In ( #3228 )
2023-03-01 15:13:24 -08:00
f839f1ed9a
clarify how to collect host.id for non-containerized systems ( #3173 )
2023-02-28 18:17:04 +01:00
90a7dae56c
Remove mention of net.transport from http semantic conventions ( #3244 )
...
Based on @lmolkova's
https://github.com/open-telemetry/opentelemetry-specification/issues/3215#issuecomment-1439068151
## Changes
Removes mention of `net.transport` from http semantic conventions.
---------
Co-authored-by: Reiley Yang <reyang@microsoft.com>
2023-02-28 10:52:04 -05: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
12481fef89
add semantic conventions for heroku ( #3075 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-02-27 10:23:29 +01:00
a0691c65ed
Rename nonheap to non_heap ( #3250 )
...
Fixes
https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/7876
(the implementation used `non_heap`, which seems better)
## Changes
Renames JVM metric attribute value from `nonheap` to `non_heap`.
---------
Co-authored-by: Carlos Alberto Cortez <calberto.cortez@gmail.com>
2023-02-24 09:59:43 -06:00
0f2a834cda
Add Connect RPC to semantic conventions ( #3116 )
...
* Add connect_rpc to rpc.yaml
* Add connect rpc into rpc-metrics and rpc markdown
* Add Connect RPC change to CHANGELOG.md
* Update CHANGELOG.md
---------
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2023-02-21 09:50:35 -05: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
1971550982
[editorial] Fix Tencent Cloud link ( #3231 )
2023-02-20 10:29:04 +01:00
702cf2cdf3
Rename Logs API to Logs Bridge API to prevent confusion ( #3197 )
...
We keep seeing confusion about what Logs API is. There was a proposal [1]
to use the term Bridge API to help prevent the confusion.
Please take a look and comment on whether you think this renaming helps
and is reasonable.
[1] https://github.com/open-telemetry/opentelemetry-specification/pull/3187#issuecomment-1424431424
2023-02-16 14:55:56 -05:00
6086a26696
Update exceptions.md ( #3217 )
2023-02-16 05:42:42 -06:00
8290599ccd
Get rid of double negation in Events semantic conventions ( #3159 )
...
* getting rid of double negation
* Update specification/logs/semantic_conventions/events.md
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
---------
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
2023-02-15 14:56:19 -05:00
a0f96da61f
Fix rpc examples to include grpc namespace ( #3211 )
2023-02-15 09:12:30 -08:00
3a0a197f4c
Use attribute_group for cross-signal HTTP attributes ( #3183 )
2023-02-13 16:00:14 -08:00
30ef366d8a
Update aws lambda spec to remove X-Ray Env propagation ( #3166 )
...
* Update aws lambda spec to remove X-Ray Env propagation
Per discussion in the FAAS SIG, we decided that the aws x-ray environment variable should be moved to a span link to avoid interfering with the configured propagators.
2023-02-10 10:57:34 -06:00
2165c692f9
Http route should contain application root ( #3164 )
2023-02-06 12:50:01 -08:00
27e087b3b6
Add http metrics yaml ( #3158 )
...
* Add http metrics yaml
* Update change log
* Fix notes
* Fix link
* Remove unnecessary field
2023-02-06 12:54:51 -05:00
9170ccaeeb
Changes to http span name ( #3165 )
2023-02-03 08:33:10 -08:00
912809fb42
Enable semantic convention tooling for metrics ( #3119 )
2023-01-24 08:52:53 -08:00
e35ad2b9d5
[semantic_conventions/resource] fix google platform openshift naming ( #3095 )
2023-01-23 14:56:48 -08:00
b45d32f1ed
Add cloud spanner and mssql compact to db specifications ( #3105 )
2023-01-23 16:18:51 -06:00
ebcf353c33
Remove rogue bracket ( #3108 )
2023-01-17 09:54:55 -08:00
708df51809
Add ClickHouse in the database group ( #3011 )
2023-01-03 19:40:09 -06:00
4de43114a4
Suggest column # as an extra source code attribute ( #3029 )
2023-01-02 18:01:32 -06:00
a7ede6fbfa
Refactor messaging attributes and specify per-message attributes ( #2957 )
2022-12-22 17:04:53 -06:00
41f5b5508b
Clarify common HTTP attributes apply to both clients and servers ( #3044 )
2022-12-16 21:48:49 +01:00
90a6aeee14
[editorial] Metrics hardware sem. conv. front matter ( #3045 )
2022-12-16 13:17:23 -06:00
656644592a
[resource] add openshift platform to all supported cloud providers ( #2985 )
2022-12-06 16:52:30 +01:00
0204860d46
Update semconv for hardware metrics to use `direction` attributes ( #2942 )
2022-12-06 00:17:54 +01:00
0adf032cf1
Add feature flagging semantic conventions ( #2529 )
2022-12-01 12:13:48 -08:00
e37e300610
Add `messaging.kafka.message.offset` attribute ( #2982 )
2022-12-01 19:21:38 +01:00
84bc1e50fc
Fix net peer name IP example address ( #2995 )
2022-12-01 18:38:24 +01:00
6f0cadac7e
List the machine-id as potential source for a unique host.id ( #2978 )
2022-11-29 10:06:04 -08:00
fa6cef115c
Rename grpc metadata attribute names to reflect that they are grpc-specific ( #2981 )
2022-11-22 15:53:34 -08:00
b901d9dd76
add ibm cloud as a cloud provider ( #2965 )
2022-11-21 10:31:32 -08:00
f517f6b17b
Make http.status_code an int ( #2943 )
2022-11-17 13:33:59 -08:00
fce78ebfc5
Move Prometheus/OpenMetrics compatibility to its own file ( #2952 )
2022-11-17 13:22:10 -08:00
43804f56d2
Track JVM gc time in histogram ( #2903 )
2022-11-15 12:53:05 -08:00
0644776443
Split out Event API from Log API ( #2941 )
...
Resolves #2917 .
Depends on #2940 .
2022-11-14 18:07:56 -05:00
acb0d5db18
Move event.domain from InstrumentationScope to LogRecord ( #2940 )
...
Resolves #2939 .
2022-11-14 10:34:49 -05:00
b334f6b070
Clarification on what an Event is, and what the event.domain and event.name attributes represent ( #2848 )
...
* Remove language around uniqueness of event names within a domain
This came up in
https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/14474
where it was highlighted that just `name` is not sufficient to provide
for uniqueness of a Kubernetes Event.
The attribute `event.domain` is only meant to be a logical separation
across different event systems, so it allows for similar looking names
in different domains but with a completely different purpose. However,
within each domain we don't have to have any uniqueness constraints on
the `name` and leave it to whatever is idiomatic to the particular event
system the domain represents.
2022-11-09 14:01:28 -05:00
07ef735d2f
s/cpu/CPU ( #2931 )
...
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
2022-11-09 17:10:44 +01:00
f9a0472bb3
Add metric for jvm memory usage after gc ( #2901 )
2022-11-08 14:02:14 -08:00
63343b5fbb
Add more semantic convention attributes for Apache RocketMQ ( #2881 )
2022-11-08 16:48:17 +01:00
9f4bd4c0b6
Add gRPC request/response metadata as span attributes ( #2874 )
2022-10-20 13:32:31 -07:00
ace15c86b6
Fix typo in http semantic conventions ( #2896 )
2022-10-20 12:36:13 -07:00
a2e925d05f
Add `process.paging.faults` metric to semantic conventions ( #2827 )
2022-10-18 15:16:37 -07:00
34093ed204
Clarify the HTTP client `http.retry_count` spec ( #2743 )
2022-10-18 10:46:16 -07:00
7c53a4e646
add daemon attribute to jvm threads metric ( #2828 )
2022-10-06 23:46:02 -07:00
7cc726cb55
Link to RPC in Metrics Semantic Conventions ( #2831 )
2022-10-06 10:27:20 -07:00
99e7370387
Changes to messaging.kafka.max.lag ( #2837 )
2022-10-04 17:02:59 -07:00
bfb8bd7a27
Fix inconsistent metric usage of http.target ( #2818 )
2022-10-03 11:16:31 -07:00
e2856b8feb
Make messaging context propagation requirements explicit ( #2750 )
2022-09-30 09:05:54 -07:00
3ce713d52b
[Logs] Add semantic conventions for writing exceptions ( #2819 )
2022-09-29 21:38:40 -07:00
ad82c3556e
Add additional process metrics to the metrics semantic conventions ( #2706 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2022-09-21 19:24:12 +02:00
c359bd372c
Add mobile and language semconv for browser resource ( #2761 )
2022-09-20 21:19:02 +02:00
8db8131112
Fix nits: incorrect unit for CPU utilization ( #2807 )
2022-09-16 10:49:58 -07:00
090f94ceb0
fix typo ( #2803 )
2022-09-15 08:32:40 -07: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
2503e776b0
Events and logs api ( #2676 )
...
This PR is a follow up to the OTEP [Events and Logs API](https://github.com/open-telemetry/oteps/blob/main/text/0202-events-and-logs-api.md ). It describes the specification for an Events and Logs API and also defines semantic conventions for attributes to be used for Events that are represented using Log Records.
For non-trivial changes, follow the [change proposal
process](../CONTRIBUTING.md#proposing-a-change) and link to the related issue(s)
and/or [OTEP(s)](https://github.com/open-telemetry/oteps ), update the
[`CHANGELOG.md`](../CHANGELOG.md), and also be sure to update
[`spec-compliance-matrix.md`](../spec-compliance-matrix.md) if necessary.
Related [OTEP(s)](https://github.com/open-telemetry/oteps ) #
[Events and Logs API](https://github.com/open-telemetry/oteps/blob/main/text/0202-events-and-logs-api.md )
2022-08-31 14:05:37 -04:00
db65960210
Add process.threads ( #2705 )
2022-08-17 18:57:03 +02:00
c26020299c
Add OpenSearch in the database group ( #2718 )
2022-08-11 20:40:03 +02:00
3d7846dc16
Add hardware-metrics to semantic conventions ( #2518 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2022-08-09 16:51:54 +02: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
fca9616e41
add process.parent_pid attribute ( #2691 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2022-07-28 16:54:58 +02:00
298c566cf9
Remove alternative attribute sets from HTTP semantic conventions ( #2469 )
2022-07-27 11:31:21 -07:00
7fcd293974
add definition for state attribute of system.network.connections ( #2663 )
2022-07-18 19:29:38 +02:00
a384ba1ec3
Make GitHub links relative for links to specification documents ( #2669 )
...
Co-authored-by: Evan Bradley <evan-bradley@users.noreply.github.com>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2022-07-18 15:52:35 +02:00
fc9219bcfe
Add JVM buffer pool semantic conventions ( #2650 )
2022-07-13 10:11:24 -07:00
216beba6cc
Define net.sock attributes and clarify logical net.peer|host.name attributes ( #2614 )
2022-07-13 10:01:44 -07:00
067a2b88b4
[editorial] Add note to Hugo front matter ( #2651 )
2022-07-08 09:12:12 +02:00
38257767a0
Add metrics for http request and response size ( #2588 )
2022-06-30 13:37:23 -05:00
2b6b31f221
Add rpc.grpc.status_code attribute to rpc metric semantic conventions ( #2604 )
2022-06-30 09:11:39 -05:00
289bdbb7e0
add metrics to replace metrics with `direction` ( #2617 )
2022-06-28 08:57:58 -07:00
31a6ecd386
FaaS conventions: make faas.document.time and faas.time attributes recommended ( #2627 )
2022-06-28 16:38:13 +02:00
a280dd8b2e
Add network metrics to process semantic conventions ( #2556 )
2022-06-22 21:46:24 -07:00
5c19b4e868
[editorial] Ensure metrics subsections have a README ( #2629 )
2022-06-22 21:31:40 -07:00
d27ed53892
cloudevents: relax requirement level for type and version ( #2618 )
2022-06-21 13:29:53 +02:00
9448396526
Add semantic conventions for GraphQL ( #2456 )
...
Add semantic conventions for GraphQL span name and attributes.
Related issues #1670
2022-06-15 15:09:08 -04:00
3f7b7d02f9
Adopt attribute requirement levels in semantic conventions ( #2594 )
2022-06-14 08:02:55 -07:00
48b522e7f3
Clarify when "count" is used instead of pluralization ( #2613 )
2022-06-13 11:33:49 -07:00
35b2b57587
Add semantic convention attributes for capturing the application layer protocol ( #2602 )
2022-06-10 19:09:54 -07:00
2681d9c7dc
Rename p.r.jvm.memory.max to p.r.jvm.memory.limit ( #2605 )
2022-06-10 08:44:42 -05:00
22406e7c05
fix typo ( #2595 )
2022-06-01 09:02:17 -07:00
8a3a853730
Add semantic conventions for jvm cpu metrics ( #2292 )
2022-05-26 20:29:02 -07:00
5f1d85a12f
Add remaining Kafka and Kafka consumer metrics. ( #2536 )
2022-05-25 20:32:33 -07:00
4fae05c1c4
Remove outdated note ( #2540 )
2022-05-24 11:51:58 -07:00
6a613c54e4
Add Resource browser attributes ( #2353 )
2022-05-19 10:57:41 -07:00
a87e50d47d
Refactor jvm classes semantic conventions ( #2550 )
2022-05-18 23:47:26 -07:00
7d2a40e537
Azure FaaS conventions. ( #2502 )
2022-05-13 12:01:20 -07:00
64e8e1c8fb
Update kafka.md ( #2537 )
2022-05-12 20:57:22 -07:00
5df0912bb2
Add prefix to Kafka metrics. ( #2528 )
2022-05-11 17:31:15 -05:00
e4e600716b
Initial addition of Kafka metrics. ( #2485 )
2022-05-09 14:12:28 -07:00
aa58aa8611
Specify how to obtain a Ruby thread's id ( #2508 )
2022-05-05 21:32:47 -07:00
9410cb6131
Fix a typo ( #2523 )
2022-05-04 16:54:00 +02:00
53ba5dd524
Map SunOS to `solaris` for `os.type` resource attribute ( #2509 )
2022-04-27 14:12:22 -07:00
6d6aa8df6e
Add HTTP/3 ( #2507 )
2022-04-27 14:09:05 -07:00
5115a5dc87
Update JVM metrics with JMX Gatherer values. ( #2478 )
2022-04-22 09:51:25 -05:00
eb7c318db3
Database connection pool metrics semantic conventions ( #2273 )
2022-04-18 17:44:41 -07:00
fc23f00281
Allow all metric conventions to be either synchronous or asynchronous. ( #2458 )
2022-04-08 11:14:29 -07:00
33b2703c32
Add net.host.name and net.host.ip to rpc server ( #2447 )
2022-04-01 22:40:05 -07:00
fc0090a6ef
Move net.peer.name from http common to http client ( #2446 )
2022-04-01 22:29:15 -07:00
7c1aa90f27
Add rpc.system value for Apache Dubbo ( #2453 )
...
* Add rpc.system value for Apache Dubbo
* Generate table
2022-03-30 15:21:53 -07:00
4d510fbc04
Add process.cpu.utilization metric ( #2436 )
...
* Add process.cpu.utilization
* Update with PR #
* fix, and more clarity
Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
2022-03-30 08:08:22 -07:00
bf7a606901
Clarify system.cpu.utilization metric definition ( #2435 )
2022-03-28 18:57:03 +02:00
2d4de7fdf2
Fix links ( #2426 )
2022-03-21 23:05:45 -07:00
003dee810b
Introduce new semantic conventions for CloudEvents ( #1978 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Co-authored-by: Johannes Tax <johannes@johannes.tax>
Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
2022-03-10 19:11:32 +01:00
20fda6a90e
Define span structure for HTTP retries and redirects ( #2078 )
...
This PR clarifies semantic conventions for HTTP retries and redirects and defines a span structure and linking as well as span attributes for retries. Changes were discussed recently at Instrumentation SIG meetings.
This change addresses a scenario which is in the scope for bringing the existing HTTP semantic conventions for tracing to an initial stable state, see related [otep #174 ](https://github.com/open-telemetry/oteps/pull/174 ).
2022-03-08 20:22:45 -05:00
741ac62a15
Bump semantic conventions tool to v0.11.0 and refine enum wording ( #2399 )
2022-03-04 17:51:37 +01:00
3aa566575f
Add table for well-known rpc.system values ( #2377 )
2022-03-03 14:38:54 +01:00
2b026d81db
Define JavaScript runtimes semantic conventions ( #2290 )
2022-03-02 16:18:40 +01:00
9c7d6d2ace
nit: Pluralize "measures" ( #2391 )
...
Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>
2022-03-01 12:50:52 -08:00
e16e1f5952
[editorial] Remove repeated sentence in trace semconv ( #2352 )
...
Context: #2236 , at https://github.com/open-telemetry/opentelemetry-specification/pull/2236/files#r807345305
2022-02-15 14:04:05 -08:00
a358a31b2a
[editorial]Add toc/tocstop to Logs pages ( #2321 )
2022-02-09 15:24:45 -05:00
8c9de82151
Pin markdownlint-cli version and apply fixes ( #2320 )
...
* Pin markdownlint-cli version
* Apply markdownlint fixes
2022-02-07 10:24:33 -08:00
d62ad18c75
Add opentracing.ref_type semantic convention. ( #2297 )
2022-01-31 11:14:02 -06:00
4f6af3ae6f
Change golang namespace to 'go', rather than 'gc' ( #2262 )
...
* Change golang namespace to 'go', rather than 'gc'
* Specify common process.runtime.* attributes for Go
* Add link to runtime.Compiler
* Remove static descriptions
* Add table of descriptions for golang runtime names
* Add context to go examples
Co-authored-by: Sergey Kanzhelev <S.Kanzhelev@live.com>
2022-01-27 07:21:21 +00:00
c76f9ddb7c
Add jvm memory runtime metrics ( #2272 )
...
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2022-01-26 18:55:47 +01:00
7a2a71849f
Add semantic conventions for process metrics ( #2061 )
...
Resolves #1817
Prerequisite for [(collector) #4232 ](https://github.com/open-telemetry/opentelemetry-collector/issues/4232 )
2022-01-25 10:49:43 -05:00
225d780d8f
Add placeholder for jvm metrics ( #2257 )
2022-01-13 23:29:09 -06:00
5799c847fb
Add link from FaaS trace to resource attributes ( #2256 )
2022-01-10 18:00:53 +00:00
6ecce73b9b
Upgrade semconv generator to v0.8.0 ( #2236 )
...
* Upgrade semconv generator to v0.8.0
* update specs with semconv gen 0.8.0
* makefile
2022-01-03 14:09:21 -08:00
3b50032ecc
Add `device.manufacturer` to semantic conventions for resources ( #2100 )
...
* Update device.md
Proposed manufacturer field
* Update device.md
* Generate tables
* PR comments
* Remove trailing whitespace
* Update CHANGELOG.md
Make linter happy?
* Fix merge
Co-authored-by: Josh Suereth <joshuasuereth@google.com>
2021-12-16 00:22:56 +00:00
fccbbba116
Clarify integer count instrument units ( #2210 )
2021-12-14 18:09:19 +00:00
7652ed48fa
Prohibit usage of retired names in semantic conventions ( #2191 )
...
* Prohibit usage of retired names in semantic conventions
This change adds a prohibition clause that requires that no old
metric or attribute name is used for a new attribute.
This is important to ensure reversibility of schema transformation
(converting from a new version to an old version of schema).
Without this restriction the following is possible:
Schema version 1. Attribute A exists.
Schema version 2. Attribute A is renamed to B. Appropriate schema file is created.
Schema version 3. Attribute A is introduced (a completely different new attribute).
Now attempting to go from Version 3 to version 1 is impossible since it requires
renaming B to A (for the change in version 2), but a different attribute A already exists.
* Fix based on comments
* Add changelog entry
Co-authored-by: Carlos Alberto Cortez <calberto.cortez@gmail.com>
2021-12-13 10:04:41 -08:00
d42c6f54a9
Use UCUM units in Metrics Semantic Conventions ( #2199 )
2021-12-13 15:45:26 +01:00
688c0e9ea4
Rename extra dimensions to extra attributes ( #2162 )
...
* Rename extra dimensions to extra attributes
* Moar
Co-authored-by: Reiley Yang <reyang@microsoft.com>
Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>
2021-12-10 12:12:10 -08:00
3c380cadeb
Update link to Prometheus Receiver Design Document ( #2211 )
...
since it was moved to opentelemetry-collector-contrib repo
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
2021-12-10 19:56:59 +00:00
99fcd04b06
Align runtime metric and resource namespaces ( #2112 )
...
A 'process.runtime' namespace is currently defined in the resource
semantic conventions. The metric semantic conventions suggest that
runtime metrics use a 'runtime' namespace. Since the runtime metrics
are directly related to the runtime resources, they ought to share a
common namespace.
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
2021-11-18 14:36:45 +00:00
76b14b16c2
Add semantic conventions for log media attributes ( #2022 )
...
Logs are transmitted via several common media, such as files and
iostreams. This PR establishes semantic conventions for describing the
file or iostream from which a log was read. Notably, these attributes
are not resource attributes, as the medium used to tranmit a log is not
considered to be the originator of the log.
2021-11-09 18:12:07 -05:00
fdd5c96846
Clarify difference between `container.name` and `k8s.container.name` ( #1980 )
...
Add more details to container name attributes to clarify the difference.
Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>
2021-11-04 18:45:20 +00:00
Robert Pająk