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
semantic-conventions/docs/general
History
Alexander Wert fde7b11e61
Moved thread and code to the registry (#434) 
Signed-off-by: Alexander Wert <alexander.wert@elastic.co>
 		2023-10-27 16:13:49 +02:00
..
README.md [editorial] Rename general section pages by dropping `general` from the filename (#195) 2023-07-14 10:10:35 -07:00
attributes.md Moved thread and code to the registry (#434) 2023-10-27 16:13:49 +02:00
events.md Editorial: random improvements (#415) 2023-10-19 16:53:57 -07:00
forward-proxy.png Rename/replace `(client|server).socket.(address|port)` attributes with `network.(peer|local).(address|port)`. (#342) 2023-10-10 17:13:16 +02:00
logs.md Bump to latest specification version. (#379) 2023-10-11 09:29:44 -04:00
metrics.md Editorial: random improvements (#415) 2023-10-19 16:53:57 -07:00
reverse-proxy.png Rename/replace `(client|server).socket.(address|port)` attributes with `network.(peer|local).(address|port)`. (#342) 2023-10-10 17:13:16 +02:00
session.md Add session.previous_id (#348) 2023-10-21 15:40:31 +02:00
simple.png Rename/replace `(client|server).socket.(address|port)` attributes with `network.(peer|local).(address|port)`. (#342) 2023-10-10 17:13:16 +02:00
trace-compatibility.md Editorial: random improvements (#415) 2023-10-19 16:53:57 -07:00
trace.md Editorial: random improvements (#415) 2023-10-19 16:53:57 -07:00

README.md

General Semantic Conventions

This document defines general Semantic Conventions for spans, metrics, logs and events.

The following general Semantic Conventions are defined:

  • General attributes: General semantic attributes.
  • Events: General Semantic Conventions for events.
  • Logs: General Semantic Conventions for logs.
  • Metrics: General Semantic Conventions for metrics.
  • Spans: General Semantic Conventions for traces / spans.

Event Name Reuse Prohibition

A new event MUST NOT be added with the same name as an event that existed in the past but was renamed (with a corresponding schema file).

When introducing a new event name check all existing schema files to make sure the name does not appear as a key of any "rename_events" section (keys denote old event names in rename operations).