Merge branch 'open-telemetry:main' into localize-content-languages-java-sdk

Author: Vinaum8

content/en/blog/2025/ottl-contexts-just-got-easier.md

@@ -83,7 +83,6 @@ benefits of context inference while providing granular control over statement
 configurations, such as `error_mode` and `conditions`. For example, consider the
 following configuration:
 
-<!-- prettier-ignore-start -->
 ```yaml
 metric_statements:
   - context: datapoint
@@ -92,35 +91,31 @@ metric_statements:
     statements:
       - set(metric.description, "counter") where attributes["my.attr"] == "some"
 ```
-<!-- prettier-ignore-end -->
 
 The above can now be written as:
 
-<!-- prettier-ignore-start -->
+<!-- prettier-ignore -->
 ```yaml
 metric_statements:
   - conditions:
       - resource.attributes["service.name"] == "my.service"
     statements:
       - set(metric.description, "counter") where datapoint.attributes["my.attr"] == "some"
 ```
-<!-- prettier-ignore-end -->
 
 In this example, the `context` value is omitted and is automatically inferred to
 `datapoint`, as it is the only OTTL context present in the statements that
 supports parsing both `datapoint` and `metric` data.
 
 If we update the above configuration removing the `datapoint` usage:
 
-<!-- prettier-ignore-start -->
 ```yaml
 metric_statements:
   - conditions:
       - resource.attributes["service.name"] == "my.service"
     statements:
       - set(metric.description, "counter")
 ```
-<!-- prettier-ignore-end -->
 
 The context inferrer would select the `metric` OTTL context instead, since no
 data points are accessed. Although it would be possible to run the statements

content/en/docs/collector/_index.md

@@ -3,7 +3,7 @@ title: Collector
 description: Vendor-agnostic way to receive, process and export telemetry data.
 aliases: [./about]
 cascade:
-  vers: 0.119.0
+  vers: 0.120.0
 weight: 270
 ---
 

content/en/docs/collector/building/receiver.md

@@ -350,7 +350,7 @@ touch tailtracer/factory.go
 ```
 
 Now let's follow the convention and add a function named `NewFactory()` that
-will be responsible to instantiate the `tailtracer` factory. Go ahead the add
+will be responsible to instantiate the `tailtracer` factory. Go ahead and add
 the following code to your `factory.go` file:
 
 ```go

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

@@ -305,7 +305,9 @@ There are currently no metrics specific to `normal` verbosity.
 {{% alert title="Note" color="info" %}} The `http_` and `rpc_` metrics come from
 instrumentation libraries. Their original names use dots (`.`), but when
 exposing internal metrics with Prometheus, they are translated to use
-underscores (`_`) to match Prometheus' naming constraints.
+underscores (`_`) to match Prometheus' naming constraints. These metrics are not
+covered by the maturity levels below since they are not under the Collector SIG
+control.
 
 The `otelcol_processor_batch_` metrics are unique to the `batchprocessor`.
 
@@ -329,6 +331,10 @@ The Collector logs the following internal events:
 
 ## Telemetry maturity levels
 
+The Collector telemetry levels apply to all first-party telemetry produced by
+the Collector. Third-party libraries, including those of OpenTelemetry Go, are
+not covered by these maturity levels.
+
 ### Traces
 
 Tracing instrumentation is still under active development, and changes might be
@@ -338,10 +344,13 @@ guarantees of backwards compatibility for tracing instrumentation.
 
 ### Metrics
 
-The Collector's metrics follow a four-stage lifecycle:
+The Collector's first-party metrics follow a four-stage lifecycle:
 
 > Alpha metric → Stable metric → Deprecated metric → Deleted metric
 
+Third-party metrics, including those generated by OpenTelemetry Go
+instrumentation libraries, are not covered by these maturity levels.
+
 #### Alpha
 
 Alpha metrics have no stability guarantees. These metrics can be modified or

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

@@ -196,8 +196,8 @@ exporters specified via `otel.traces.exporter`:
 | System property                  | Description                                                     | Default |
 | -------------------------------- | --------------------------------------------------------------- | ------- |
 | `otel.bsp.schedule.delay`        | The interval, in milliseconds, between two consecutive exports. | `5000`  |
-| `otel.bsp.max.queue.size`        | The maximum queue size.                                         | `2048`  |
-| `otel.bsp.max.export.batch.size` | The maximum batch size.                                         | `512`   |
+| `otel.bsp.max.queue.size`        | The maximum number of spans that can be queued before batching. | `2048`  |
+| `otel.bsp.max.export.batch.size` | The maximum number of spans to export in a single batch.        | `512`   |
 | `otel.bsp.export.timeout`        | The maximum allowed time, in milliseconds, to export data.      | `30000` |
 
 Properties for [sampler](../sdk/#sampler):
@@ -256,12 +256,12 @@ Properties for cardinality limits:
 Properties for [log record processor(s)](../sdk/#logrecordprocessor) pared with
 exporters via `otel.logs.exporter`:
 
-| System property                   | Description                                                     | Default |
-| --------------------------------- | --------------------------------------------------------------- | ------- |
-| `otel.blrp.schedule.delay`        | The interval, in milliseconds, between two consecutive exports. | `1000`  |
-| `otel.blrp.max.queue.size`        | The maximum queue size.                                         | `2048`  |
-| `otel.blrp.max.export.batch.size` | The maximum batch size.                                         | `512`   |
-| `otel.blrp.export.timeout`        | The maximum allowed time, in milliseconds, to export data.      | `30000` |
+| System property                   | Description                                                           | Default |
+| --------------------------------- | --------------------------------------------------------------------- | ------- |
+| `otel.blrp.schedule.delay`        | The interval, in milliseconds, between two consecutive exports.       | `1000`  |
+| `otel.blrp.max.queue.size`        | The maximum number of log records that can be queued before batching. | `2048`  |
+| `otel.blrp.max.export.batch.size` | The maximum number of log records to export in a single batch.        | `512`   |
+| `otel.blrp.export.timeout`        | The maximum allowed time, in milliseconds, to export data.            | `30000` |
 
 #### Properties: exporters
 

content/en/docs/security/_index.md

@@ -1,7 +1,7 @@
 ---
 title: Security
 cascade:
-  collector_vers: 0.119.0
+  collector_vers: 0.120.0
 weight: 970
 ---
 

data/ecosystem/vendors.yaml

@@ -306,6 +306,12 @@
   contact:
   oss: false
   commercial: true
+- name: Parseable
+  nativeOTLP: true
+  url: https://www.parseable.com/docs/server/opentelemetry
+  contact: [email protected]
+  oss: true
+  commercial: true
 - name: qryn
   nativeOTLP: true
   url: https://qryn.metrico.in/#/support?id=tempo-api

static/refcache.json

@@ -6439,6 +6439,34 @@
     "StatusCode": 206,
     "LastSeen": "2025-02-10T19:32:07.109251077Z"
   },
+  "https://github.com/open-telemetry/opentelemetry-collector/blob/v0.120.0/component/config.go": {
+    "StatusCode": 206,
+    "LastSeen": "2025-02-19T19:17:45.009325266Z"
+  },
+  "https://github.com/open-telemetry/opentelemetry-collector/blob/v0.120.0/component/config.go#L50": {
+    "StatusCode": 206,
+    "LastSeen": "2025-02-19T19:17:42.775563833Z"
+  },
+  "https://github.com/open-telemetry/opentelemetry-collector/blob/v0.120.0/pdata/internal/data/protogen/trace/v1/trace.pb.go": {
+    "StatusCode": 206,
+    "LastSeen": "2025-02-19T19:17:51.838725231Z"
+  },
+  "https://github.com/open-telemetry/opentelemetry-collector/blob/v0.120.0/pdata/pcommon/map.go": {
+    "StatusCode": 206,
+    "LastSeen": "2025-02-19T19:17:55.427696696Z"
+  },
+  "https://github.com/open-telemetry/opentelemetry-collector/blob/v0.120.0/receiver/receiver.go": {
+    "StatusCode": 206,
+    "LastSeen": "2025-02-19T19:17:50.788198899Z"
+  },
+  "https://github.com/open-telemetry/opentelemetry-collector/blob/v0.120.0/receiver/receiver.go#L58": {
+    "StatusCode": 206,
+    "LastSeen": "2025-02-19T19:17:50.094394779Z"
+  },
+  "https://github.com/open-telemetry/opentelemetry-collector/blob/v0.120.0/semconv/v1.9.0/generated_resource.go": {
+    "StatusCode": 206,
+    "LastSeen": "2025-02-19T19:17:58.227636872Z"
+  },
   "https://github.com/open-telemetry/opentelemetry-collector/issues/10469": {
     "StatusCode": 206,
     "LastSeen": "2025-02-01T07:12:41.436253-05:00"
@@ -18091,6 +18119,10 @@
     "StatusCode": 200,
     "LastSeen": "2025-01-13T11:43:58.450234-05:00"
   },
+  "https://www.parseable.com/docs/server/opentelemetry": {
+    "StatusCode": 200,
+    "LastSeen": "2025-02-20T22:54:09.030696452Z"
+  },
   "https://www.phoenixframework.org/": {
     "StatusCode": 200,
     "LastSeen": "2025-01-13T11:43:26.18526-05:00"