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/trace/semantic_conventions
History
Anuraag Agrawal 9a1b74f9c1 Add semantic conventions for http content size (#641) 
* Add semantic conventions for http content size

* Suffix not midfix
 		2020-06-25 18:02:02 -04:00
..
README.md Link from trace (and metric) semantic conventions to resources (#603) 2020-05-14 10:11:11 -07:00
database.md Move specifications into sub-directories per signal (#546) 2020-04-06 17:25:53 -04:00
faas.md Add span attribute to indicate cold starts of Function as a Service executions (#650) 2020-06-15 11:15:02 -07:00
http.md Add semantic conventions for http content size (#641) 2020-06-25 18:02:02 -04:00
messaging.md Clarify messaging.system. (#558) 2020-04-22 07:35:51 -07:00
rpc.md Extend semantic conventions for RPC and allow non-gRPC calls (#604) 2020-06-17 10:58:26 -07:00
span-general.md Move specifications into sub-directories per signal (#546) 2020-04-06 17:25:53 -04:00

README.md

Trace Semantic Conventions

In OpenTelemetry spans can be created freely and it’s up to the implementor to annotate them with attributes specific to the represented operation. Spans represent specific operations in and between systems. Some of these operations represent calls that use well-known protocols like HTTP or database calls. Depending on the protocol and the type of operation, additional information is needed to represent and analyze a span correctly in monitoring systems. It is also important to unify how this attribution is made in different languages. This way, the operator will not need to learn specifics of a language and telemetry collected from polyglot (multi-language) micro-service environments can still be easily correlated and cross-analyzed.

The following semantic conventions for spans are defined:

  • General: General semantic attributes that may be used in describing different kinds of operations.
  • HTTP: Spans for HTTP client and server.
  • Database: Spans for SQL and NoSQL client calls.
  • RPC/RMI: Spans for remote procedure calls (e.g., gRPC).
  • Messaging: Spans for interaction with messaging systems (queues, publish/subscribe, etc.).
  • FaaS: Spans for Function as a Service (e.g., AWS Lambda).

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