Merge pull request #2377 from splunk/pwilliams-fix-404s

Fix broken links

Author: pauljwil

gdi/get-data-in/application/span-attributes.rst

@@ -20,21 +20,21 @@ Semantic conventions
 
 The following semantic conventions apply for spans:
 
-- :new-page:`General <https://github.com/open-telemetry/semantic-conventions/blob/main/model/general.yaml>`: General semantic attributes that might be used in describing different kinds of operations.
+- :new-page:`General <https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/attributes.md>`: General semantic attributes that might be used in describing different kinds of operations.
 
-- :new-page:`HTTP <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/http.yaml>`: For HTTP client and server spans.
+- :new-page:`HTTP <https://github.com/open-telemetry/semantic-conventions/blob/main/model/http/spans.yaml>`: For HTTP client and server spans.
 
-- :new-page:`Database <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/database.yaml>`: For SQL and NoSQL client call spans.
+- :new-page:`Database <https://github.com/open-telemetry/semantic-conventions/blob/main/model/database/spans.yaml>`: For SQL and NoSQL client call spans.
 
-- :new-page:`RPC/RMI <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/rpc.yaml>`: For remote procedure call (for example, gRPC) spans.
+- :new-page:`RPC/RMI <https://github.com/open-telemetry/semantic-conventions/blob/main/model/rpc/spans.yaml>`: For remote procedure call (for example, gRPC) spans.
 
-- :new-page:`Messaging <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/messaging.yaml>`: For messaging system spans (queues, publish/subscribe, and so on).
+- :new-page:`Messaging <https://github.com/open-telemetry/semantic-conventions/blob/main/model/messaging/spans.yaml>`: For messaging system spans (queues, publish/subscribe, and so on).
 
-- :new-page:`FaaS <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/faas.yaml>`: For Function as a Service (for example, AWS Lambda) spans.
+- :new-page:`FaaS <https://github.com/open-telemetry/semantic-conventions/blob/main/model/faas/spans.yaml>`: For Function as a Service (for example, AWS Lambda) spans.
 
-- :new-page:`Exceptions <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/trace-exception.yaml>`: For recording exceptions associated with a span.
+- :new-page:`Exceptions <https://github.com/open-telemetry/semantic-conventions/blob/main/model/exceptions/events.yaml>`: For recording exceptions associated with a span.
 
-- :new-page:`Compatibility <https://github.com/open-telemetry/semantic-conventions/blob/main/model/trace/compatibility.yaml>`: For spans generated by compatibility components. For example, OpenTracing Shim layer.
+- :new-page:`Compatibility <https://github.com/open-telemetry/semantic-conventions/blob/main/model/opentracing/common.yaml>`: For spans generated by compatibility components. For example, OpenTracing Shim layer.
 
 Learn more about OpenTelemetry in the OpenTelemetry official documentation, such as library-specific semantic conventions for AWS Lambda, AWS SDK, or GraphQL.
 

gdi/opentelemetry/common-config/collector-common-config-auth.rst

@@ -20,7 +20,7 @@ You can configure two types of authentication for the Collector:
   * :ref:`oauth2client-extension`
   * Sigv4 extension
 
-.. note:: For more details see :new-page:`Auth Configuration Settings https://github.com/open-telemetry/opentelemetry-collector/tree/main/config/configauth` in OTel's GitHub repo.
+.. note:: For more details see :new-page:`Auth Configuration Settings <https://github.com/open-telemetry/opentelemetry-collector/tree/main/config/configauth>` in OTel's GitHub repo.
 
 Example
 =============================================================================================

gdi/opentelemetry/common-config/collector-common-config-grcp.rst

@@ -21,7 +21,7 @@ To configure gRCP clients in :ref:`exporters <otel-components-exporters>` use th
 
   * Defaults: ``pick_first`` before version 0.103.0, ``round_robin`` for v0.103.0 or higher 
 
-  * Learn more at gRCP's :new-page:`Load Balancing README https://github.com/grpc/grpc-go/blob/master/examples/features/load_balancing/README.md`. 
+  * Learn more at gRCP's :new-page:`Load Balancing README <https://github.com/grpc/grpc-go/blob/master/examples/features/load_balancing/README.md>`. 
 
 * ``compression`` 
 

gdi/opentelemetry/tags.rst

@@ -101,14 +101,14 @@ Containers
 
 There are numerous attributes for services running in containers, such as ``container.id``, ``container.name``, or ``container.image.name``. 
 
-Learn more in the OpenTelemetry GitHub repo at :new-page:`Container semantic conventions <https://github.com/open-telemetry/semantic-conventions/blob/main/model/resource/container.yaml>`.
+Learn more in the OpenTelemetry GitHub repo at :new-page:`Container semantic conventions <https://github.com/open-telemetry/semantic-conventions/blob/main/model/container/resources.yaml>`.
 
 Hosts
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 There are numerous attributes for services running in hosts, such as ``host.id``, ``host.name``, or ``host.arch``. 
 
-Learn more in the OpenTelemetry GitHub repo at :new-page:`Host semantic conventions <https://github.com/open-telemetry/semantic-conventions/blob/main/model/resource/host.yaml>`.
+Learn more in the OpenTelemetry GitHub repo at :new-page:`Host semantic conventions <https://github.com/open-telemetry/semantic-conventions/blob/main/model/host/resources.yaml>`.
 
 Deployment environment
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -122,7 +122,7 @@ Cloud
 
 There are attributes that capture information for services running in public cloud environments, such ``cloud.provider``, ``cloud.account.id``, or ``cloud.region``.
 
-Learn more in the OpenTelemetry GitHub repo at :new-page:`Cloud semantic conventions <https://github.com/open-telemetry/semantic-conventions/blob/main/model/resource/cloud.yaml>`.
+Learn more in the OpenTelemetry GitHub repo at :new-page:`Cloud semantic conventions <https://github.com/open-telemetry/semantic-conventions/blob/main/model/cloud/resources.yaml>`.
 
 .. caution:: Some cloud providers, such as GCP, define semantic conventions specific to their offering. Check Google official documentation for more information.