Added the missing vector fields in the node stats of Autoops (#48365) (#48398)

* Added the missing vector fields in the node stats of Autoops

* Apply suggestions from code review



---------


(cherry picked from commit 7c2c72e)

Co-authored-by: Amit Khandelwal <154884619+elasticblr@users.noreply.github.com>
Co-authored-by: Chris Earle <pickypg@users.noreply.github.com>

Author: 3 people

changelog/fragments/1767867708-autoops-agent-add-missing-vector-metrics.yaml

@@ -0,0 +1,45 @@
+# REQUIRED
+# Kind can be one of:
+# - breaking-change: a change to previously-documented behavior
+# - deprecation: functionality that is being removed in a later release
+# - bug-fix: fixes a problem in a previous version
+# - enhancement: extends functionality but does not break or fix existing behavior
+# - feature: new functionality
+# - known-issue: problems that we are aware of in a given version
+# - security: impacts on the security of a product or a user’s deployment.
+# - upgrade: important information for someone upgrading from a prior version
+# - other: does not fit into any of the other categories
+kind: bug-fix
+
+# REQUIRED for all kinds
+# Change summary; a 80ish characters long description of the change.
+summary: added missing vector metrics in autoops agent
+
+# REQUIRED for breaking-change, deprecation, known-issue
+# Long description; in case the summary is not enough to describe the change
+# this field accommodate a description without length limits.
+# description:
+
+# REQUIRED for breaking-change, deprecation, known-issue
+# impact:
+
+# REQUIRED for breaking-change, deprecation, known-issue
+# action:
+
+# REQUIRED for all kinds
+# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc.
+component: metricbeat
+
+# AUTOMATED
+# OPTIONAL to manually add other PR URLs
+# PR URL: A link the PR that added the changeset.
+# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added.
+# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number.
+# Please provide it if you are adding a fragment for a different PR.
+# pr: https://github.com/owner/repo/1234
+
+# AUTOMATED
+# OPTIONAL to manually add other issue URLs
+# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of).
+# If not present is automatically filled by the tooling with the issue linked to the PR number.
+# issue: https://github.com/owner/repo/1234

x-pack/metricbeat/module/autoops_es/_meta/test/cluster_info.9.2.0.json

@@ -0,0 +1,17 @@
+{
+    "name": "instance-0000000000",
+    "cluster_name": "my_cluster",
+    "cluster_uuid": "GZbSUUMQQI-A7UcGS6vCMa",
+    "version": {
+        "number": "9.2.0",
+        "build_flavor": "default",
+        "build_type": "docker",
+        "build_hash": "25d88452371273dd27356c98598287b669a03eae",
+        "build_date": "2025-10-21T10:06:21.288851013Z",
+        "build_snapshot": false,
+        "lucene_version": "10.3.1",
+        "minimum_wire_compatibility_version": "8.19.0",
+        "minimum_index_compatibility_version": "8.0.0"
+    },
+    "tagline": "You Know, for Search"
+}

x-pack/metricbeat/module/autoops_es/metricset/_meta/test/success.9.2.0.json

@@ -0,0 +1,12 @@
+{
+    "items": [
+        {
+            "name": "obj1",
+            "value": 1
+        },
+        {
+            "name": "obj2",
+            "value": 2
+        }
+    ]
+}

x-pack/metricbeat/module/autoops_es/node_stats/_meta/test/master_node.9.2.0.json

@@ -0,0 +1,3 @@
+{
+    "master_node": "ek46S1GsSK2ajJ8xAnTtrA"
+}