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/specification/logs/semantic_conventions
History
Tigran Najaryan 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
..
README.md Events and logs api (#2676) 2022-08-31 14:05:37 -04:00
events.md Get rid of double negation in Events semantic conventions (#3159) 2023-02-15 14:56:19 -05:00
exceptions.md Rename Logs API to Logs Bridge API to prevent confusion (#3197) 2023-02-16 14:55:56 -05:00
feature-flags.md Rename Logs API to Logs Bridge API to prevent confusion (#3197) 2023-02-16 14:55:56 -05:00
media.md Make GitHub links relative for links to specification documents (#2669) 2022-07-18 15:52:35 +02:00

README.md

Log Attribute Semantic Conventions

Status: Experimental

The following semantic conventions for logs are defined:

  • Log Media: Semantic attributes that may be used in describing the source of a log.

The following semantic conventions for events are defined:

  • Events: Semantic attributes that must be used to represent Events using log data model.

Apart from semantic conventions for logs, traces, and metrics, OpenTelemetry also defines the concept of overarching Resources with their own Resource Semantic Conventions.