[Azure Logs] Clarify event hub name field description (#9258)

* Clarify event hub name field description

Recent feedback indicates confusion among users who mistakenly input
the Event Hub Namespace instead of the Event Hub Name in the relevant
field.

To address this and enhance user understanding, this commit makes the
following adjustments to the field's description:

- Clearly defines the purpose of the field: Specifies that users
  should enter the name of the Event Hub they wish to connect to.
- Delineates what the field is not for: Explicitly states that
  this field is not intended for the Event Hub Namespace name.

This distinction is crucial to prevent the recurrence of the
confusion and to ensure that the field is used as intended.

---------

Co-authored-by: Arianna Laudazzi <[email protected]>

packages/azure/changelog.yml

@@ -1,3 +1,8 @@
+- version: "1.11.1"
+  changes:
+    - description: Update description for event hub parameter name recommendations.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/9258
 - version: "1.11.0"
   changes:
     - description: Use ecs definition of the 'event.dataset' field for eventhub
@@ -415,7 +420,7 @@
     - description: Add spring cloud logs
       type: enhancement
       link: https://github.com/elastic/integrations/pull/1355
-- version: '0.6.2'
+- version: "0.6.2"
   changes:
     - description: update to ECS 1.11.0
       type: enhancement

packages/azure/manifest.yml

@@ -1,6 +1,6 @@
 name: azure
 title: Azure Logs
-version: 1.11.0
+version: 1.11.1
 description: This Elastic integration collects logs from Azure
 type: integration
 icons:
@@ -25,12 +25,12 @@ screenshots:
 vars:
   - name: eventhub
     type: text
-    title: Event Hub
+    title: Event Hub Name
     multi: false
     required: true
     show_user: true
     description: >-
-      Elastic recommends using one event hub for each integration. Visit [Create an event hub](https://docs.elastic.co/integrations/azure#create-an-event-hub) to learn more. Use event hub names up to 30 characters long to avoid compatibility issues.
+      The event hub name that contains the logs to ingest. Do not use the event hub namespace here. Elastic recommends using one event hub for each integration. Visit [Create an event hub](https://docs.elastic.co/integrations/azure#create-an-event-hub) to learn more. Use event hub names up to 30 characters long to avoid compatibility issues.
   - name: consumer_group
     type: text
     title: Consumer Group

packages/azure_metrics/data_stream/monitor/fields/package-fields.yml

@@ -70,7 +70,6 @@
       description: |
         Autogenerated ID representing the fingerprint of the azure.dimensions object
       dimension: true
-
     - name: metrics.*.*
       type: object
       object_type: float

packages/azure_metrics/data_stream/storage_account/fields/agent.yml

@@ -166,5 +166,5 @@
     - name: os.codename
       type: keyword
       example: "stretch"
-      description: >
-        OS codename, if any.
+      description: >-
+        OS codename, if any.

packages/azure_metrics/data_stream/storage_account/fields/fields.yml

@@ -3,5 +3,5 @@
   object_type: float
   metric_type: gauge
   object_type_mapping_type: "*"
-  description: >
-    storage account
+  description: >-
+    storage account

packages/azure_metrics/data_stream/storage_account/fields/package-fields.yml

@@ -93,7 +93,6 @@
           type: keyword
           dimension: true
           description: Type of transaction. The available values include User and System.
-
     - name: metrics.*.*
       type: object
       object_type: float