IBM-MQ added dimension fields (#6466)

* IBM-MQ added dimension fields

packages/ibmmq/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "0.6.0"
+  changes:
+    - description: Added dimension fields for qmgr datastream for TSDB enablement
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/6466
 - version: "0.5.0"
   changes:
     - description: Rename ownership from obs-service-integrations to obs-infraobs-integrations

packages/ibmmq/data_stream/qmgr/fields/ecs.yml

@@ -18,7 +18,32 @@
   name: event.type
 - external: ecs
   name: service.address
+  dimension: true
 - external: ecs
   name: service.type
 - external: ecs
   name: tags
+- external: ecs
+  name: agent.id
+  dimension: true
+- external: ecs
+  name: cloud.account.id
+  dimension: true
+- external: ecs
+  name: cloud.region
+  dimension: true
+- external: ecs
+  name: cloud.availability_zone
+  dimension: true
+- external: ecs
+  name: cloud.instance.id
+  dimension: true
+- external: ecs
+  name: cloud.provider
+  dimension: true
+- external: ecs
+  name: container.id
+  dimension: true
+- external: ecs
+  name: host.name
+  dimension: true

packages/ibmmq/data_stream/qmgr/fields/fields.yml

@@ -272,8 +272,12 @@
       type: group
       fields:
         - name: job
+          #Reason to add as dimension field: Job name identifies the name of the job. Multi-value exists
           type: keyword
+          dimension: true
           description: Prometheus label job.
         - name: qmgr
           type: keyword
+          #Reason to add as dimension field: Multiple queue managers can be configured.
+          dimension: true
           description: Name of Queue Manager.

packages/ibmmq/docs/README.md

@@ -319,6 +319,13 @@ An example event for `qmgr` looks as following:
 | Field | Description | Type |
 |---|---|---|
 | @timestamp | Event timestamp. | date |
+| agent.id | Unique identifier of this agent (if one exists). Example: For Beats this would be beat.id. | keyword |
+| cloud.account.id | The cloud account or organization id used to identify different entities in a multi-tenant environment. Examples: AWS account id, Google Cloud ORG Id, or other unique identifier. | keyword |
+| cloud.availability_zone | Availability zone in which this host, resource, or service is located. | keyword |
+| cloud.instance.id | Instance ID of the host machine. | keyword |
+| cloud.provider | Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean. | keyword |
+| cloud.region | Region in which this host, resource, or service is located. | keyword |
+| container.id | Unique container id. | keyword |
 | data_stream.dataset | Data stream dataset. | constant_keyword |
 | data_stream.namespace | Data stream namespace. | constant_keyword |
 | data_stream.type | Data stream type. | constant_keyword |
@@ -331,6 +338,7 @@ An example event for `qmgr` looks as following:
 | event.module | Name of the module this data is coming from. If your monitoring agent supports the concept of modules or plugins to process events of a given source (e.g. Apache logs), `event.module` should contain the name of this module. | keyword |
 | event.outcome | This is one of four ECS Categorization Fields, and indicates the lowest level in the ECS category hierarchy. `event.outcome` simply denotes whether the event represents a success or a failure from the perspective of the entity that produced the event. Note that when a single transaction is described in multiple events, each event may populate different values of `event.outcome`, according to their perspective. Also note that in the case of a compound event (a single event that contains multiple logical events), this field should be populated with the value that best captures the overall success or failure from the perspective of the event producer. Further note that not all events will have an associated outcome. For example, this field is generally not populated for metric events, events with `event.type:info`, or any events for which an outcome does not make logical sense. | keyword |
 | event.type | This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy. `event.type` represents a categorization "sub-bucket" that, when used along with the `event.category` field values, enables filtering events down to a level appropriate for single visualization. This field is an array. This will allow proper categorization of some events that fall in multiple event types. | keyword |
+| host.name | Name of the host. It can contain what `hostname` returns on Unix systems, the fully qualified domain name, or a name specified by the user. The sender decides which value to use. | keyword |
 | ibmmq.labels.job | Prometheus label job. | keyword |
 | ibmmq.labels.qmgr | Name of Queue Manager. | keyword |
 | ibmmq.qmgr.calls.failed.callback.count | Failed MQCB count. | long |

packages/ibmmq/manifest.yml

@@ -1,7 +1,7 @@
 format_version: 1.0.0
 name: ibmmq
 title: IBM MQ
-version: "0.5.0"
+version: "0.6.0"
 license: basic
 description: Collect logs and metrics from IBM MQ with Elastic Agent.
 type: integration