Merge branch 'main' into pt_translate_concepts_distributions

assets/scss/_styles_project.scss

@@ -125,8 +125,11 @@
       max-width: 80%;
     }
 
-    a.external-link:after {
-      display: none;
+    a {
+      color: white;
+      &.external-link:after {
+        display: none;
+      }
     }
   }
 }

content/en/_index.md

@@ -28,7 +28,6 @@ show_banner: true
 
 - [Learn more](docs/what-is-opentelemetry/)
 - [Try the demo](docs/demo/)
-- [Explore integrations](/ecosystem/integrations/)
 
 </div>
 
@@ -49,32 +48,37 @@ OpenTelemetry is a collection of APIs, SDKs, and tools. Use it to instrument,
 generate, collect, and export telemetry data (metrics, logs, and traces) to help
 you analyze your software's performance and behavior.
 
-> OpenTelemetry is **generally available** across
-> [several languages](docs/languages/) and is suitable for use.
+> OpenTelemetry is [generally available](/status/) across
+> [several languages](docs/languages/) and is suitable for production use.
 
 {{% /blocks/lead %}}
 
 {{% blocks/section color="dark" type="row" %}}
 
-{{% blocks/feature icon="fas fa-chart-line" title="Traces, Metrics, Logs"%}}
+{{% blocks/feature icon="fas fa-chart-line" title="Traces, Metrics, Logs" url="docs/concepts/observability-primer/" %}}
 
-Create and collect telemetry data from your services and software, then forward
-them to a variety of analysis tools. {{% /blocks/feature %}}
+Create and collect telemetry from your services and software, then forward it to
+a variety of analysis tools.
 
-{{% blocks/feature icon="fas fa-magic" title="Drop-In Instrumentation"%}}
+{{% /blocks/feature %}}
+
+{{% blocks/feature icon="fas fa-magic" title="Drop-in Instrumentation & Integrations" %}}
 
-OpenTelemetry integrates with popular libraries and frameworks such as
-[Spring](https://spring.io),
-[ASP.NET Core](https://docs.microsoft.com/aspnet/core),
-[Express](https://expressjs.com), [Quarkus](https://quarkus.io), and more!
-Installation and integration can be as simple as a few lines of code.
+OpenTelemetry [integrates] with many popular libraries and frameworks, and
+supports _code-based and zero-code_ [instrumentation].
+
+[instrumentation]: /docs/concepts/instrumentation/
+[integrates]: /ecosystem/integrations/
 
 {{% /blocks/feature %}}
 
 {{% blocks/feature icon="fab fa-github" title="Open Source, Vendor Neutral" %}}
 
-100% Free and Open Source, OpenTelemetry is adopted and supported by
-[industry leaders](/ecosystem/vendors/) in the observability space.
+100% free and open source, OpenTelemetry is [adopted] and supported by [industry
+leaders] in the observability space.
+
+[adopted]: /ecosystem/adopters/
+[industry leaders]: /ecosystem/vendors/
 
 {{% /blocks/feature %}}
 

content/en/docs/collector/internal-telemetry.md

@@ -283,7 +283,8 @@ own telemetry.
 
 #### Data loss
 
-Use the rate of `otelcol_processor_dropped_spans > 0` and
+Use the rate of `otelcol_processor_dropped_log_records > 0`,
+`otelcol_processor_dropped_spans > 0`, and
 `otelcol_processor_dropped_metric_points > 0` to detect data loss. Depending on
 your project's requirements, select a narrow time window before alerting begins
 to avoid notifications for small losses that are within the desired reliability
@@ -317,19 +318,22 @@ logs for messages such as `Dropping data because sending_queue is full`.
 
 #### Receive failures
 
-Sustained rates of `otelcol_receiver_refused_spans` and
-`otelcol_receiver_refused_metric_points` indicate that too many errors were
-returned to clients. Depending on the deployment and the clients' resilience,
-this might indicate clients' data loss.
+Sustained rates of `otelcol_receiver_refused_log_records`,
+`otelcol_receiver_refused_spans`, and `otelcol_receiver_refused_metric_points`
+indicate that too many errors were returned to clients. Depending on the
+deployment and the clients' resilience, this might indicate clients' data loss.
 
-Sustained rates of `otelcol_exporter_send_failed_spans` and
+Sustained rates of `otelcol_exporter_send_failed_log_records`,
+`otelcol_exporter_send_failed_spans`, and
 `otelcol_exporter_send_failed_metric_points` indicate that the Collector is not
 able to export data as expected. These metrics do not inherently imply data loss
 since there could be retries. But a high rate of failures could indicate issues
 with the network or backend receiving the data.
 
 #### Data flow
 
-You can monitor data ingress with the `otelcol_receiver_accepted_spans` and
-`otelcol_receiver_accepted_metric_points` metrics and data egress with the
-`otelcol_exporter_sent_spans` and `otelcol_exporter_sent_metric_points` metrics.
+You can monitor data ingress with the `otelcol_receiver_accepted_log_records`,
+`otelcol_receiver_accepted_spans`, and `otelcol_receiver_accepted_metric_points`
+metrics and data egress with the `otelcol_exporter_sent_log_records`,
+`otelcol_exporter_sent_spans`, and `otelcol_exporter_sent_metric_points`
+metrics.

content/en/docs/languages/java/_index.md

@@ -7,7 +7,7 @@ aliases: [/java, /java/metrics, /java/tracing]
 cascade:
   vers:
     instrumentation: 2.7.0
-    otel: 1.41.0
+    otel: 1.42.0
     semconv: 1.27.0
 weight: 18
 ---

content/en/ecosystem/integrations.md

@@ -18,8 +18,8 @@ ultimately all applications should either integrate the OpenTelemetry APIs and
 SDKs directly for native telemetry, or provide a first-party plugin that fits
 into the ecosystem of the given software.
 
-On this page you will find a sample of libraries, services and apps, that
-provide such a native instrumentation or first class plugin.
+This page contains a sample of libraries, services, and apps providing native
+instrumentation or first class plugins.
 
 ## Libraries
 
@@ -36,9 +36,9 @@ The following list contains a sample of libraries, services, and apps that have
 either integrated OpenTelemetry APIs and SDKs directly for native telemetry or
 provide a first-party plugin that fits into their own extensibility ecosystem.
 
-You will find open source (OSS) projects at the beginning of the list;
-commercial projects follow. Projects which are part of the
-[CNCF](https://www.cncf.io/) show a small CNCF logo beside their name.
+Open source projects (OSS) are at the beginning of the list, and commercial
+projects follow. Projects which are part of the [CNCF](https://www.cncf.io/)
+have a CNCF logo beside their name.
 
 {{% ecosystem/integrations-table "application integrations" %}}
 

data/registry/exporter-dotnet-onecollector.yml

@@ -18,4 +18,4 @@ createdAt: 2023-03-03
 package:
   registry: nuget
   name: OpenTelemetry.Exporter.OneCollector
-  version: 1.9.2
+  version: 1.10.0-alpha.1

data/registry/exporter-js-instana.yml

@@ -15,4 +15,4 @@ createdAt: 2022-04-18
 package:
   registry: npm
   name: '@instana/opentelemetry-exporter'
-  version: 3.17.1
+  version: 3.18.0