open-telemetry
/
semantic-conventions
mirror of https://github.com/open-telemetry/semantic-conventions.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
535 Commits 2 Branches 18 Tags 34 MiB
Commit Graph

535 Commits

Author SHA1 Message Date
Trask Stalnaker 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
Trask Stalnaker 9170ccaeeb Changes to http span name (#3165) 2023-02-03 08:33:10 -08:00
Armin Ruech 912809fb42 Enable semantic convention tooling for metrics (#3119) 2023-01-24 08:52:53 -08:00
Ben B e35ad2b9d5 [semantic_conventions/resource] fix google platform openshift naming (#3095) 2023-01-23 14:56:48 -08:00
Michael Murphy b45d32f1ed Add cloud spanner and mssql compact to db specifications (#3105) 2023-01-23 16:18:51 -06:00
Martin Costello ebcf353c33 Remove rogue bracket (#3108) 2023-01-17 09:54:55 -08:00
Carlos Alberto Cortez 54ca902e06 Update the 1.17 Schema to reference the proper changes PR (#3099) 2023-01-12 20:01:16 -06:00
v-electrolux 708df51809 Add ClickHouse in the database group (#3011) 2023-01-03 19:40:09 -06:00
jordigh 4de43114a4 Suggest column # as an extra source code attribute (#3029) 2023-01-02 18:01:32 -06:00
Liudmila Molkova a7ede6fbfa Refactor messaging attributes and specify per-message attributes (#2957) 2022-12-22 17:04:53 -06:00
Armin Ruech 41f5b5508b Clarify common HTTP attributes apply to both clients and servers (#3044) 2022-12-16 21:48:49 +01:00
Patrice Chalin 90a6aeee14 [editorial] Metrics hardware sem. conv. front matter (#3045) 2022-12-16 13:17:23 -06:00
Carlos Alberto Cortez 3f3308305b Add 1.16.0 Schema. (#3016) 2022-12-08 00:37:22 +01:00
Ben B 656644592a [resource] add openshift platform to all supported cloud providers (#2985) 2022-12-06 16:52:30 +01:00
Bertrand Martin 0204860d46 Update semconv for hardware metrics to use `direction` attributes (#2942) 2022-12-06 00:17:54 +01:00
Michael Beemer 0adf032cf1 Add feature flagging semantic conventions (#2529) 2022-12-01 12:13:48 -08:00
Mateusz Rzeszutek e37e300610 Add `messaging.kafka.message.offset` attribute (#2982) 2022-12-01 19:21:38 +01:00
Tyler Yahn 84bc1e50fc Fix net peer name IP example address (#2995) 2022-12-01 18:38:24 +01:00
Severin Neumann 6f0cadac7e List the machine-id as potential source for a unique host.id (#2978) 2022-11-29 10:06:04 -08:00
Trask Stalnaker fa6cef115c Rename grpc metadata attribute names to reflect that they are grpc-specific (#2981) 2022-11-22 15:53:34 -08:00
Ben B b901d9dd76 add ibm cloud as a cloud provider (#2965) 2022-11-21 10:31:32 -08:00
Alan West f517f6b17b Make http.status_code an int (#2943) 2022-11-17 13:33:59 -08:00
David Ashpole fce78ebfc5 Move Prometheus/OpenMetrics compatibility to its own file (#2952) 2022-11-17 13:22:10 -08:00
jack-berg 43804f56d2 Track JVM gc time in histogram (#2903) 2022-11-15 12:53:05 -08:00
jack-berg 0644776443 Split out Event API from Log API (#2941) 
Resolves #2917.

Depends on #2940.
 2022-11-14 18:07:56 -05:00
jack-berg acb0d5db18 Move event.domain from InstrumentationScope to LogRecord (#2940) 
Resolves #2939.
 2022-11-14 10:34:49 -05:00
Santosh Cheler 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
Reiley Yang 07ef735d2f s/cpu/CPU (#2931) 
Co-authored-by: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
 2022-11-09 17:10:44 +01:00
jack-berg f9a0472bb3 Add metric for jvm memory usage after gc (#2901) 2022-11-08 14:02:14 -08:00
Aaron Ai 63343b5fbb Add more semantic convention attributes for Apache RocketMQ (#2881) 2022-11-08 16:48:17 +01:00
Bogdan Drutu bfda5b34b7 Define semantic conventions yaml for non-otlp conventions (#2850) 
* Define semantic conventions yaml for non-otlp conventions

Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>

* Update semantic_conventions/trace/exporter/exporter.yaml

Co-authored-by: Christian Neumüller <christian+github@neumueller.me>

* Update semantic_conventions/scope/exporter/exporter.yaml

Co-authored-by: Joao Grassi <joao@joaograssi.com>

* Rename otel to otel_span

Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>

Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
Co-authored-by: Christian Neumüller <christian+github@neumueller.me>
Co-authored-by: Joao Grassi <joao@joaograssi.com>
 2022-10-25 08:46:06 -07:00
Sami Musallam 9f4bd4c0b6 Add gRPC request/response metadata as span attributes (#2874) 2022-10-20 13:32:31 -07:00
Liudmila Molkova ace15c86b6 Fix typo in http semantic conventions (#2896) 2022-10-20 12:36:13 -07:00
Andrzej Stencel a2e925d05f Add `process.paging.faults` metric to semantic conventions (#2827) 2022-10-18 15:16:37 -07:00
Mateusz Rzeszutek 34093ed204 Clarify the HTTP client `http.retry_count` spec (#2743) 2022-10-18 10:46:16 -07:00
Tigran Najaryan 6ea1e8d355 Verify that schema files are correctly published (#2868) 
This downloads the schema files from https://opentelemetry.io/schemas/ and verifies their content.

Next time we make a release this will force us to make sure
https://github.com/open-telemetry/opentelemetry.io repo is updated
before we make the release.

This helps prevent issues like https://github.com/open-telemetry/opentelemetry.io/issues/1846

Also add release procedure to the docs.
 2022-10-17 17:06:25 -04:00
Hao Tu 7c53a4e646 add daemon attribute to jvm threads metric (#2828) 2022-10-06 23:46:02 -07:00
Glenn Oppegard 7cc726cb55 Link to RPC in Metrics Semantic Conventions (#2831) 2022-10-06 10:27:20 -07:00
Trask Stalnaker 99e7370387 Changes to messaging.kafka.max.lag (#2837) 2022-10-04 17:02:59 -07:00
Carlos Alberto Cortez d4943b2d14 Release 1.14.0 (#2851) 2022-10-04 23:27:17 +02:00
jack-berg bfb8bd7a27 Fix inconsistent metric usage of http.target (#2818) 2022-10-03 11:16:31 -07:00
Joao Grassi e2856b8feb Make messaging context propagation requirements explicit (#2750) 2022-09-30 09:05:54 -07:00
Mikel Blanchard 3ce713d52b [Logs] Add semantic conventions for writing exceptions (#2819) 2022-09-29 21:38:40 -07:00
Evan Bradley 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
Santosh Cheler c359bd372c Add mobile and language semconv for browser resource (#2761) 2022-09-20 21:19:02 +02:00
Reiley Yang 8db8131112 Fix nits: incorrect unit for CPU utilization (#2807) 2022-09-16 10:49:58 -07:00
Georg Pirklbauer 090f94ceb0 fix typo (#2803) 2022-09-15 08:32:40 -07:00
Aaron Ai 8d5a30e353 Fix a lot of typos (#2778) 2022-09-09 08:48:59 -07:00
Tigran Najaryan 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
Santosh Cheler 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