ActiveMQ added dimensions for broker datastream (#6484)

* ActiveMQ added dimensions for broker datastream

packages/activemq/changelog.yml

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

packages/activemq/data_stream/broker/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/activemq/data_stream/broker/fields/fields.yml

@@ -9,6 +9,7 @@
       description: Number of message consumers.
     - name: mbean
       type: keyword
+      dimension: true
       description: MBean that this event is related to.
     - name: memory
       type: group
@@ -39,6 +40,7 @@
           description: Number of messages that have been sent to the destination.
     - name: name
       type: keyword
+      dimension: true
       description: Broker name.
     - name: producers.count
       type: long

packages/activemq/docs/README.md

@@ -356,6 +356,13 @@ An example event for `broker` looks as following:
 | activemq.broker.messages.enqueue.count | Number of messages that have been sent to the destination. | long |  |
 | activemq.broker.name | Broker name. | keyword |  |
 | activemq.broker.producers.count | Number of message producers active on destinations on the broker. | long |  |
+| 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 |  |
@@ -368,6 +375,7 @@ An example event for `broker` looks as following:
 | event.kind | This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy. `event.kind` gives high-level information about what type of information the event contains, without being specific to the contents of the event. For example, values of this field distinguish alert events from metric events. The value of this field can be used to inform how these kinds of events should be handled. They may warrant different retention, different access control, it may also help understand whether the data coming in at a regular interval or not. | keyword |  |
 | 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.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 |  |
 | service.address | Address where data about this service was collected from. This should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets). | keyword |  |
 | service.type | The type of the service data is collected from. The type can be used to group and correlate logs and metrics from one service type. Example: If logs or metrics are collected from Elasticsearch, `service.type` would be `elasticsearch`. | keyword |  |
 | tags | List of keywords used to tag each event. | keyword |  |

packages/activemq/manifest.yml

@@ -1,6 +1,6 @@
 name: activemq
 title: ActiveMQ
-version: "0.8.0"
+version: "0.9.0"
 description: Collect logs and metrics from ActiveMQ instances with Elastic Agent.
 type: integration
 icons:
@@ -115,4 +115,4 @@ policy_templates:
         title: Collect ActiveMQ broker, queue and topic metrics
         description: Collecting broker, queue and topic metrics from ActiveMQ instances.
 owner:
-  github: elastic/obs-infraobs-integrations
+  github: elastic/obs-infraobs-integrations