Moved Exceptions semconv (#147)

.github/CODEOWNERS

@@ -21,6 +21,7 @@
 
 # Logs semantic conventions
 /semantic_conventions/logs/                  @open-telemetry/specs-semconv-approvers @tigrannajaryan
+/specification/exceptions/exceptions-logs.md @open-telemetry/specs-semconv-approvers @tigrannajaryan
 /specification/general/events-general.md     @open-telemetry/specs-semconv-approvers @tigrannajaryan
 /specification/general/logs-general.md       @open-telemetry/specs-semconv-approvers @tigrannajaryan
 /specification/logs/                         @open-telemetry/specs-semconv-approvers @tigrannajaryan

specification/README.md

@@ -7,6 +7,7 @@ The benefit to using Semantic Conventions is in following a common naming scheme
 Semantic Conventions are defined for the following areas:
 
 * [General](general/README.md): General Semantic Conventions.
+* [Exceptions](exceptions/README.md): Semantic Conventions for Exceptions.
 * [HTTP](http/README.md): Semantic Conventions for HTTP client and server operations.
 * [Database](database/README.md): Semantic Conventions for database operations.
 * *Other areas can be found in the signal specific Semantic Conventions below*

specification/exceptions/README.md

@@ -0,0 +1,12 @@
+# Semantic conventions for Exceptions
+
+**Status**: [Experimental][DocumentStatus]
+
+This document defines semantic conventions for Exceptions.
+
+Semantic conventions for Exceptions are defined for the following signals:
+
+* [Exceptions on spans](exceptions-spans.md): Semantic Conventions for Exceptions associated with *spans*.
+* [Exceptions in logs](exceptions-logs.md): Semantic Conventions for Exceptions recorded in *logs*.
+
+[DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md

specification/exceptions/exceptions-logs.md

@@ -1,4 +1,4 @@
-# Semantic Conventions for Exceptions
+# Semantic Conventions for Exceptions in Logs
 
 **Status**: [Experimental][DocumentStatus]
 
@@ -47,6 +47,6 @@ The table below indicates which attributes should be added to the
 ### Stacktrace Representation
 
 Same as [Trace Semantic Conventions for Exceptions - Stacktrace
-Representation](../../trace/semantic_conventions/exceptions.md#stacktrace-representation).
+Representation](exceptions-spans.md#stacktrace-representation).
 
 [DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md

specification/exceptions/exceptions-spans.md

@@ -1,9 +1,9 @@
-# Semantic Conventions for Exceptions
+# Semantic Conventions for Exceptions on Spans
 
 **Status**: [Experimental][DocumentStatus]
 
 This document defines semantic conventions for recording application
-exceptions.
+exceptions associated with spans.
 
 <!-- toc -->
 
@@ -102,7 +102,7 @@ grained information from a stacktrace, if necessary.
 [ruby-full-message]: https://ruby-doc.org/core-2.7.1/Exception.html#method-i-full_message
 [csharp-stacktrace]: https://docs.microsoft.com/en-us/dotnet/api/system.exception.tostring
 [go-stacktrace]: https://pkg.go.dev/runtime/debug#Stack
-[telemetry-sdk-resource]: ../../resource/semantic_conventions/README.md#telemetry-sdk
+[telemetry-sdk-resource]: ../resource/semantic_conventions/README.md#telemetry-sdk
 [erlang-stacktrace]: https://www.erlang.org/doc/man/erl_error.html#format_exception-3
 [elixir-stacktrace]: https://hexdocs.pm/elixir/1.14.3/Exception.html#format/3
 [DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md

specification/general/events-general.md

@@ -8,7 +8,7 @@ in the data model by `LogRecord`s.
 The following semantic conventions for events are defined:
 
 * [General](#general-event-attributes): General semantic attributes that may be used in describing Events.
-* [Exceptions](/specification/logs/semantic_conventions/exceptions.md): Semantic attributes that may be used in describing exceptions as events.
+* [Exceptions](/specification/exceptions/exceptions-logs.md): Semantic attributes that may be used in describing exceptions as events.
 
 ## General event attributes
 

specification/general/logs-general.md

@@ -19,7 +19,7 @@ They may be used in any Log Record they apply to.
 The following semantic conventions for logs are defined:
 
 * [General](#general-log-identification-attributes): General semantic attributes that may be used in describing Log Records.
-* [Exceptions](/specification/logs/semantic_conventions/exceptions.md): Semantic attributes that may be used in describing exceptions in logs.
+* [Exceptions](/specification/exceptions/exceptions-logs.md): Semantic attributes that may be used in describing exceptions in logs.
 * [Feature Flags](/specification/logs/semantic_conventions/feature-flags.md): Semantic attributes that may be used in describing feature flag evaluations in logs.
 
 Apart from semantic conventions for logs, [events](events-general.md), [traces](trace-general.md), and [metrics](metrics-general.md),

specification/general/trace-general.md

@@ -21,7 +21,7 @@ The following semantic conventions for spans are defined:
 * [RPC/RMI](/specification/trace/semantic_conventions/rpc.md): For remote procedure call (e.g., gRPC) spans.
 * [Messaging](/specification/trace/semantic_conventions/messaging.md): For messaging systems (queues, publish/subscribe, etc.) spans.
 * [FaaS](/specification/trace/semantic_conventions/faas.md): For [Function as a Service](https://en.wikipedia.org/wiki/Function_as_a_service) (e.g., AWS Lambda) spans.
-* [Exceptions](/specification/trace/semantic_conventions/exceptions.md): For recording exceptions associated with a span.
+* [Exceptions](/specification/exceptions/exceptions-spans.md): For recording exceptions associated with a span.
 * [Compatibility](trace-compatibility.md): For spans generated by compatibility components, e.g. OpenTracing Shim layer.
 * [Feature Flags](/specification/trace/semantic_conventions/feature-flags.md): For recording feature flag evaluations associated with a span.