Merge branch 'main' into feat-otelcol-receiver-github

Author: matt-gp

docs/sources/reference/components/beyla/beyla.ebpf.md

@@ -65,6 +65,8 @@ The following formats are supported:
 
 You can use the following blocks with `beyla.ebpf`:
 
+{{< docs/alloy-config >}}
+
 | Block                                                                  | Description                                                                                        | Required |
 |------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|----------|
 | [`output`][output]                                                     | Configures where to send received telemetry data.                                                  | yes      |
@@ -100,9 +102,6 @@ You can use the following blocks with `beyla.ebpf`:
 | `injector` > [`resources`][injector resources]                         | Configures resource attributes for the injected SDK.                                               | no       |
 | `injector` > [`sampler`][sampler]                                      | Configures default trace sampling for injected SDKs.                                               | no       |
 
-The > symbol indicates deeper levels of nesting.
-For example, `attributes` > `kubernetes` refers to a `kubernetes` block defined inside an `attributes` block.
-
 [routes]: #routes
 [traces]: #traces
 [attributes]: #attributes
@@ -127,6 +126,8 @@ For example, `attributes` > `kubernetes` refers to a `kubernetes` block defined
 [injector export]: #export
 [injector resources]: #resources
 
+{{< /docs/alloy-config >}}
+
 ### `output`
 
 {{< badge text="Required" >}}

docs/sources/reference/components/database_observability/database_observability.mysql.md

@@ -54,6 +54,8 @@ The following collectors are configurable:
 
 You can use the following blocks with `database_observability.mysql`:
 
+{{< docs/alloy-config >}}
+
 | Block                                | Description                                       | Required |
 |--------------------------------------|---------------------------------------------------|----------|
 | [`cloud_provider`][cloud_provider]   | Provide Cloud Provider information.               | no       |
@@ -68,9 +70,6 @@ You can use the following blocks with `database_observability.mysql`:
 | [`query_samples`][query_samples]     | Configure the query samples collector.            | no       |
 | [`health_check`][health_check]       | Configure the health check collector.             | no       |
 
-The > symbol indicates deeper levels of nesting.
-For example, `cloud_provider` > `aws` refers to a `aws` block defined inside an `cloud_provider` block.
-
 [cloud_provider]: #cloud_provider
 [aws]: #aws
 [azure]: #azure
@@ -83,6 +82,8 @@ For example, `cloud_provider` > `aws` refers to a `aws` block defined inside an
 [setup_actors]: #setup_actors
 [health_check]: #health_check
 
+{{< /docs/alloy-config >}}
+
 ### `cloud_provider`
 
 The `cloud_provider` block has no attributes.

docs/sources/reference/components/database_observability/database_observability.postgres.md

@@ -65,6 +65,8 @@ The following collectors are configurable:
 
 You can use the following blocks with `database_observability.postgres`:
 
+{{< docs/alloy-config >}}
+
 | Block                              | Description                                       | Required |
 |------------------------------------|---------------------------------------------------|----------|
 | [`cloud_provider`][cloud_provider] | Provide Cloud Provider information.               | no       |
@@ -76,9 +78,6 @@ You can use the following blocks with `database_observability.postgres`:
 | [`explain_plans`][explain_plans]   | Configure the explain plans collector.            | no       |
 | [`health_check`][health_check]     | Configure the health check collector.             | no       |
 
-The > symbol indicates deeper levels of nesting.
-For example, `cloud_provider` > `aws` refers to a `aws` block defined inside an `cloud_provider` block.
-
 [cloud_provider]: #cloud_provider
 [aws]: #aws
 [azure]: #azure
@@ -88,6 +87,8 @@ For example, `cloud_provider` > `aws` refers to a `aws` block defined inside an
 [explain_plans]: #explain_plans
 [health_check]: #health_check
 
+{{< /docs/alloy-config >}}
+
 ### `cloud_provider`
 
 The `cloud_provider` block has no attributes.

docs/sources/reference/components/discovery/discovery.azure.md

@@ -47,18 +47,22 @@ You can use the following arguments with `discovery.azure`:
 
 You can use the following blocks with `discovery.azure`:
 
+{{< docs/alloy-config >}}
+
 | Block                                  | Description                                      | Required |
 | -------------------------------------- | ------------------------------------------------ | -------- |
 | [`managed_identity`][managed_identity] | Managed Identity configuration for Azure API.    | no       |
 | [`oauth`][oauth]                       | OAuth 2.0 configuration for Azure API.           | no       |
 | [`tls_config`][tls_config]             | TLS configuration for requests to the Azure API. | no       |
 
-You must specify exactly one of the `oauth` or `managed_identity` blocks.
-
 [managed_identity]: #managed_identity
 [oauth]: #oauth
 [tls_config]: #tls_config
 
+{{< /docs/alloy-config >}}
+
+You must specify exactly one of the `oauth` or `managed_identity` blocks.
+
 ### `managed_identity`
 
 The `managed_identity` block configures Managed Identity authentication for the Azure API.

docs/sources/reference/components/discovery/discovery.consul.md

@@ -71,6 +71,8 @@ At most, one of the following can be provided:
 
 You can use the following blocks with `discovery.consul`:
 
+{{< docs/alloy-config >}}
+
 | Block                                 | Description                                                | Required |
 | ------------------------------------- | ---------------------------------------------------------- | -------- |
 | [`authorization`][authorization]      | Configure generic authorization to the endpoint.           | no       |
@@ -79,14 +81,13 @@ You can use the following blocks with `discovery.consul`:
 | `oauth2` > [`tls_config`][tls_config] | Configure TLS settings for connecting to the endpoint.     | no       |
 | [`tls_config`][tls_config]            | Configure TLS settings for connecting to the endpoint.     | no       |
 
-The > symbol indicates deeper levels of nesting.
-For example, `oauth2` > `tls_config` refers to a `tls_config` block defined inside an `oauth2` block.
-
 [authorization]: #authorization
 [basic_auth]: #basic_auth
 [oauth2]: #oauth2
 [tls_config]: #tls_config
 
+{{< /docs/alloy-config >}}
+
 ### `authorization`
 
 The `authorization` block configures generic authorization to the endpoint.

docs/sources/reference/components/discovery/discovery.consulagent.md

@@ -47,12 +47,16 @@ You can use the following arguments with `discovery.consulagent`:
 
 You can use the following block with `discovery.consulagent`:
 
+{{< docs/alloy-config >}}
+
 | Block                      | Description                                            | Required |
 | -------------------------- | ------------------------------------------------------ | -------- |
 | [`tls_config`][tls_config] | Configure TLS settings for connecting to the endpoint. | no       |
 
 [tls_config]: #tls_config
 
+{{< /docs/alloy-config >}}
+
 ### `tls_config`
 
 The `tls_config` block configures TLS settings for connecting to the endpoint.

docs/sources/reference/components/discovery/discovery.docker.md

@@ -61,6 +61,8 @@ At most, one of the following can be provided:
 
 You can use the following blocks with `discovery.docker`:
 
+{{< docs/alloy-config >}}
+
 | Block                                 | Description                                                | Required |
 | ------------------------------------- | ---------------------------------------------------------- | -------- |
 | [`authorization`][authorization]      | Configure generic authorization to the endpoint.           | no       |
@@ -70,15 +72,14 @@ You can use the following blocks with `discovery.docker`:
 | `oauth2` > [`tls_config`][tls_config] | Configure TLS settings for connecting to the endpoint.     | no       |
 | [`tls_config`][tls_config]            | Configure TLS settings for connecting to the endpoint.     | no       |
 
-The > symbol indicates deeper levels of nesting.
-For example, `oauth2` > `tls_config` refers to a `tls_config` block defined inside an `oauth2` block.
-
 [filter]: #filter
 [basic_auth]: #basic_auth
 [authorization]: #authorization
 [oauth2]: #oauth2
 [tls_config]: #tls_config
 
+{{< /docs/alloy-config >}}
+
 ### `authorization`
 
 The `authorization` block configures generic authorization to the endpoint.

docs/sources/reference/components/discovery/discovery.dockerswarm.md

@@ -59,6 +59,8 @@ At most, one of the following can be provided:
 
 You can use the following blocks with `discovery.dockerswarm`:
 
+{{< docs/alloy-config >}}
+
 | Block                                 | Description                                                                        | Required |
 | ------------------------------------- | ---------------------------------------------------------------------------------- | -------- |
 | [`authorization`][authorization]      | Configure generic authorization to the endpoint.                                   | no       |
@@ -68,15 +70,14 @@ You can use the following blocks with `discovery.dockerswarm`:
 | `oauth2` > [`tls_config`][tls_config] | Configure TLS settings for connecting to the endpoint.                             | no       |
 | [`tls_config`][tls_config]            | Configure TLS settings for connecting to the endpoint.                             | no       |
 
-The `>` symbol indicates deeper levels of nesting.
-For example, `oauth2 > tls_config` refers to a `tls_config` block defined inside an `oauth2` block.
-
 [filter]: #filter
 [basic_auth]: #basic_auth
 [authorization]: #authorization
 [oauth2]: #oauth2
 [tls_config]: #tls_config
 
+{{< /docs/alloy-config >}}
+
 ### `authorization`
 
 The `authorization` block configures generic authorization to the endpoint.

docs/sources/reference/components/discovery/discovery.ec2.md

@@ -62,6 +62,8 @@ At most, one of the following can be provided:
 
 You can use the following blocks with `discovery.ec2`:
 
+{{< docs/alloy-config >}}
+
 | Block                                 | Description                                                | Required |
 | ------------------------------------- | ---------------------------------------------------------- | -------- |
 | [`authorization`][authorization]      | Configure generic authorization to the endpoint.           | no       |
@@ -71,15 +73,14 @@ You can use the following blocks with `discovery.ec2`:
 | `oauth2` > [`tls_config`][tls_config] | Configure TLS settings for connecting to the endpoint.     | no       |
 | [`tls_config`][tls_config]            | Configure TLS settings for connecting to the endpoint.     | no       |
 
-The > symbol indicates deeper levels of nesting.
-For example, `oauth2` > `tls_config` refers to a `tls_config` block defined inside an `oauth2` block.
-
 [authorization]: #authorization
 [basic_auth]: #basic_auth
 [filter]: #filter
 [oauth2]: #oauth2
 [tls_config]: #tls_config
 
+{{< /docs/alloy-config >}}
+
 ### `authorization`
 
 The `authorization` block configures generic authorization to the endpoint.

docs/sources/reference/components/discovery/discovery.eureka.md

@@ -58,6 +58,8 @@ At most, one of the following can be provided:
 
 You can use the following blocks with `discovery.eureka`:
 
+{{< docs/alloy-config >}}
+
 | Block                                 | Description                                                | Required |
 | ------------------------------------- | ---------------------------------------------------------- | -------- |
 | [`authorization`][authorization]      | Configure generic authorization to the endpoint.           | no       |
@@ -66,14 +68,13 @@ You can use the following blocks with `discovery.eureka`:
 | `oauth2` > [`tls_config`][tls_config] | Configure TLS settings for connecting to the endpoint.     | no       |
 | [`tls_config`][tls_config]            | Configure TLS settings for connecting to the endpoint.     | no       |
 
-The > symbol indicates deeper levels of nesting.
-For example, `oauth2` > `tls_config` refers to a `tls_config` block defined inside an `oauth2` block.
-
 [authorization]: #authorization
 [basic_auth]: #basic_auth
 [oauth2]: #oauth2
 [tls_config]: #tls_config
 
+{{< /docs/alloy-config >}}
+
 ### `authorization`
 
 The `authorization` block configures generic authorization to the endpoint.