[chore] Add display names for receivers - batch 10

receiver/vcrreceiver/README.md

@@ -1,6 +1,11 @@
+<!-- status autogenerated section -->
 # VCR Receiver
 
-<!-- status autogenerated section -->
+The OpenTelemetry **Verbatim Capture & Replay (VCR) toolset** enables full-fidelity capture and replay of all
+telemetry data stored on disk. It replays previously captured telemetry while **preserving original event timestamps**,
+allowing you to simulate realistic traffic timing independent of when the data was captured.
+
+
 | Status        |           |
 | ------------- |-----------|
 | Stability     | [development]: traces, metrics, logs, profiles   |
@@ -14,8 +19,6 @@
 
 ## Overview
 
-The OpenTelemetry **Verbatim Capture & Replay (VCR) toolset** enables full-fidelity capture and replay of all telemetry data stored on disk. It replays previously captured telemetry while **preserving original event timestamps**, allowing you to simulate realistic traffic timing independent of when the data was captured.
-
 The receiver reads telemetry from JSON files stored in a **"TAPE" (Telemetry Archive for Playback & Emulation)**. Each tape contains OpenTelemetry data encoded using **Protobuf JSON** and follows the OpenTelemetry Protocol (OTLP).
 
 ### 1. Raw Input Files

receiver/vcrreceiver/metadata.yaml

@@ -1,5 +1,11 @@
+display_name: VCR Receiver
 type: vcr
 
+description: |
+  The OpenTelemetry **Verbatim Capture & Replay (VCR) toolset** enables full-fidelity capture and replay of all
+  telemetry data stored on disk. It replays previously captured telemetry while **preserving original event timestamps**,
+  allowing you to simulate realistic traffic timing independent of when the data was captured.
+
 status:
   class: receiver
   stability:

receiver/wavefrontreceiver/README.md

@@ -1,6 +1,5 @@
-# Wavefront Receiver
-
 <!-- status autogenerated section -->
+# Wavefront Receiver
 | Status        |           |
 | ------------- |-----------|
 | Stability     | [deprecated]: metrics   |

receiver/wavefrontreceiver/metadata.yaml

@@ -1,3 +1,4 @@
+display_name: Wavefront Receiver
 type: wavefront
 
 status:

receiver/webhookeventreceiver/README.md

@@ -1,6 +1,12 @@
+<!-- status autogenerated section -->
 # Webhook Event Receiver
 
-<!-- status autogenerated section -->
+The Webhook Event Receiver is a push based event collector component meant to act as a generally available receiver
+for any webhook style data source. It is designed to work alongside other pipeline components like the
+[transform processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/transformprocessor)
+to allow the ingestion of generic events as logs into the opentelemetry collector.
+
+
 | Status        |           |
 | ------------- |-----------|
 | Stability     | [beta]: logs   |
@@ -13,10 +19,6 @@
 [contrib]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib
 <!-- end autogenerated section -->
 
-The Webhook Event Receiver is a push based event collector component meant to act as a generally available receiver for any webhook style data source. It is designed to work alongside other pipeline components
-like the [transform processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/transformprocessor) to allow the ingestion of generic events as logs into the opentelemetry 
-collector.
-
 ## Configuration
 
 The following settings are required:

receiver/webhookeventreceiver/metadata.yaml

@@ -1,5 +1,12 @@
+display_name: Webhook Event Receiver
 type: webhookevent
 
+description: |
+  The Webhook Event Receiver is a push based event collector component meant to act as a generally available receiver
+  for any webhook style data source. It is designed to work alongside other pipeline components like the
+  [transform processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/transformprocessor)
+  to allow the ingestion of generic events as logs into the opentelemetry collector.
+
 status:
   class: receiver
   stability:

receiver/windowseventlogreceiver/README.md

@@ -1,6 +1,10 @@
-## Windows Event Log Receiver
-
 <!-- status autogenerated section -->
+# Windows Event Log Receiver
+
+This receiver tails and parses logs from windows event log API using the
+[opentelemetry-log-collection](https://github.com/open-telemetry/opentelemetry-log-collection) library.
+
+
 | Status        |           |
 | ------------- |-----------|
 | Stability     | [alpha]: logs   |
@@ -14,8 +18,6 @@
 [contrib]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib
 <!-- end autogenerated section -->
 
-Tails and parses logs from windows event log API using the [opentelemetry-log-collection](https://github.com/open-telemetry/opentelemetry-log-collection) library.
-
 ### Configuration Fields
 
 | Field                               | Default      | Description                                                                                                                                                                                                                                    |

receiver/windowseventlogreceiver/metadata.yaml

@@ -1,5 +1,10 @@
+display_name: Windows Event Log Receiver
 type: windowseventlog
 
+description: |
+  This receiver tails and parses logs from windows event log API using the
+  [opentelemetry-log-collection](https://github.com/open-telemetry/opentelemetry-log-collection) library.
+
 status:
   class: receiver
   stability:

receiver/windowsperfcountersreceiver/README.md

@@ -1,6 +1,11 @@
+<!-- status autogenerated section -->
 # Windows Performance Counters Receiver
 
-<!-- status autogenerated section -->
+This receiver, for Windows only, captures the configured system, application, or
+custom performance counter data from the Windows registry using the [PDH
+interface](https://docs.microsoft.com/en-us/windows/win32/perfctrs/using-the-pdh-functions-to-consume-counter-data).
+
+
 | Status        |           |
 | ------------- |-----------|
 | Stability     | [beta]: metrics   |
@@ -14,10 +19,7 @@
 [contrib]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib
 <!-- end autogenerated section -->
 
-This receiver, for Windows only, captures the configured system, application, or
-custom performance counter data from the Windows registry using the [PDH
-interface](https://docs.microsoft.com/en-us/windows/win32/perfctrs/using-the-pdh-functions-to-consume-counter-data).
-It is based on the [Telegraf Windows Performance Counters Input
+This receiver is based on the [Telegraf Windows Performance Counters Input
 Plugin](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/win_perf_counters).
 
 If one of the specified performance counters cannot be loaded on startup, a

receiver/windowsperfcountersreceiver/metadata.yaml

@@ -1,5 +1,11 @@
+display_name: Windows Performance Counters Receiver
 type: windowsperfcounters
 
+description: |
+  This receiver, for Windows only, captures the configured system, application, or
+  custom performance counter data from the Windows registry using the [PDH
+  interface](https://docs.microsoft.com/en-us/windows/win32/perfctrs/using-the-pdh-functions-to-consume-counter-data).
+
 status:
   class: receiver
   stability:

receiver/windowsservicereceiver/README.md

@@ -1,6 +1,10 @@
+<!-- status autogenerated section -->
 # Windows Service Receiver
 
-<!-- status autogenerated section -->
+The Windows Service Receiver is a receiver for scraping information about the state of services running on a Windows
+machine.
+
+
 | Status        |           |
 | ------------- |-----------|
 | Stability     | [development]: metrics   |
@@ -14,8 +18,6 @@
 [contrib]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib
 <!-- end autogenerated section -->
 
-The Windows Service Receiver is a receiver for scraping information about the state of services running on a Windows machine.
-
 ## Getting Started
 
 By default the Windows Service Receiver will attempt to identify and monitor the status of all specified services on the host machine.

receiver/windowsservicereceiver/metadata.yaml

@@ -1,5 +1,10 @@
+display_name: Windows Service Receiver
 type: windowsservice
 
+description: |
+  The Windows Service Receiver is a receiver for scraping information about the state of services running on a Windows
+  machine.
+
 status:
   class: receiver
   stability:

receiver/yanggrpcreceiver/README.md

@@ -1,6 +1,11 @@
-# YANG gRPC receiver
-
 <!-- status autogenerated section -->
+# YANG gRPC Receiver
+
+The YANG/gRPC receiver receives metrics offered using the
+[YANG (Yet Another New Generation) data model](https://en.wikipedia.org/wiki/YANG), expressed over
+[gRPC](https://ciscolearning.github.io/cisco-learning-codelabs/posts/yangsuite-restconf/#0).
+
+
 | Status        |           |
 | ------------- |-----------|
 | Stability     | [alpha]: metrics   |
@@ -13,9 +18,7 @@
 [contrib]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib
 <!-- end autogenerated section -->
 
-The YANG/gRPC receiver receives metrics offered using the [YANG (Yet Another New Generation) data model](https://en.wikipedia.org/wiki/YANG), expressed over [gRPC](https://ciscolearning.github.io/cisco-learning-codelabs/posts/yangsuite-restconf/#0).
-
-The receiver exposes a gRPC endpoint, accepting the gRPC configuration offered by the [configgrpc](https://pkg.go.dev/go.opentelemetry.io/collector/config/configgrpc) module.
+This receiver exposes a gRPC endpoint, accepting the gRPC configuration offered by the [configgrpc](https://pkg.go.dev/go.opentelemetry.io/collector/config/configgrpc) module.
 
 # Configuration
 

receiver/yanggrpcreceiver/metadata.yaml

@@ -1,6 +1,12 @@
+display_name: YANG gRPC Receiver
 type: yang_grpc
 deprecated_type: yanggrpc
 
+description: |
+  The YANG/gRPC receiver receives metrics offered using the
+  [YANG (Yet Another New Generation) data model](https://en.wikipedia.org/wiki/YANG), expressed over
+  [gRPC](https://ciscolearning.github.io/cisco-learning-codelabs/posts/yangsuite-restconf/#0).
+
 status:
   class: receiver
   stability:

receiver/zipkinreceiver/README.md

@@ -1,6 +1,9 @@
+<!-- status autogenerated section -->
 # Zipkin Receiver
 
-<!-- status autogenerated section -->
+This receiver receives spans from [Zipkin](https://zipkin.io/) (V1 and V2).
+
+
 | Status        |           |
 | ------------- |-----------|
 | Stability     | [beta]: traces   |
@@ -15,8 +18,6 @@
 [k8s]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-k8s
 <!-- end autogenerated section -->
 
-This receiver receives spans from [Zipkin](https://zipkin.io/) (V1 and V2).
-
 ## Getting Started
 
 All that is required to enable the Zipkin receiver is to include it in the

receiver/zipkinreceiver/metadata.yaml

@@ -1,5 +1,9 @@
+display_name: Zipkin Receiver
 type: zipkin
 
+description: |
+  This receiver receives spans from [Zipkin](https://zipkin.io/) (V1 and V2).
+
 status:
   class: receiver
   stability:

receiver/zookeeperreceiver/README.md

@@ -1,6 +1,10 @@
+<!-- status autogenerated section -->
 # Zookeeper Receiver
 
-<!-- status autogenerated section -->
+The Zookeeper Receiver collects metrics from a Zookeeper instance, using the `mntr` command. The `mntr` 4 letter word
+command needs to be enabled for the receiver to be able to collect metrics.
+
+
 | Status        |           |
 | ------------- |-----------|
 | Stability     | [alpha]: metrics   |
@@ -14,9 +18,6 @@
 [contrib]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib
 <!-- end autogenerated section -->
 
-The Zookeeper receiver collects metrics from a Zookeeper instance, using the `mntr` command. The `mntr` 4 letter word command needs
-to be enabled for the receiver to be able to collect metrics.
-
 ## Configuration
 
 - `endpoint`: (default = `localhost:2181`) Endpoint to connect to collect metrics. Takes the form `host:port`. See our [security best practices doc](https://opentelemetry.io/docs/security/config-best-practices/#protect-against-denial-of-service-attacks) to understand how to set the endpoint in different environments.

receiver/zookeeperreceiver/metadata.yaml

@@ -1,5 +1,10 @@
+display_name: Zookeeper Receiver
 type: zookeeper
 
+description: |
+  The Zookeeper Receiver collects metrics from a Zookeeper instance, using the `mntr` command. The `mntr` 4 letter word
+  command needs to be enabled for the receiver to be able to collect metrics.
+
 status:
   class: receiver
   stability:

scraper/zookeeperscraper/README.md

@@ -1,6 +1,10 @@
+<!-- status autogenerated section -->
 # Zookeeper Scraper
 
-<!-- status autogenerated section -->
+The Zookeeper scraper collects metrics from a Zookeeper instance, using the `mntr` command. The `mntr` 4 letter word
+command needs to be enabled for the scraper to be able to collect metrics.
+
+
 | Status        |           |
 | ------------- |-----------|
 | Stability     | [alpha]: metrics   |
@@ -14,9 +18,6 @@
 [contrib]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib
 <!-- end autogenerated section -->
 
-The Zookeeper scraper collects metrics from a Zookeeper instance, using the `mntr` command. The `mntr` 4 letter word command needs
-to be enabled for the scraper to be able to collect metrics.
-
 ## Configuration
 
 - `endpoint`: (default = `localhost:2181`) Endpoint to connect to collect metrics. Takes the form `host:port`. See our [security best practices doc](https://opentelemetry.io/docs/security/config-best-practices/#protect-against-denial-of-service-attacks) to understand how to set the endpoint in different environments.

scraper/zookeeperscraper/metadata.yaml

@@ -1,5 +1,10 @@
+display_name: Zookeeper Scraper
 type: zookeeper
 
+description: |
+  The Zookeeper scraper collects metrics from a Zookeeper instance, using the `mntr` command. The `mntr` 4 letter word
+  command needs to be enabled for the scraper to be able to collect metrics.
+
 status:
   class: scraper
   stability: