Pulling refs/heads/main into main

gdi/monitors-hosts/vsphere.rst

@@ -123,8 +123,8 @@ See the following example with extended config options:
 Configuration settings
 ~~~~~~~~~~~~~~~~~~~~~~
 
-The following table shows the configuration options for the ``vsphere``
-monitor:
+The following table shows the main configuration options for the ``vsphere``
+monitor. For more settings see :new-page:`vSphere monitor <https://github.com/signalfx/signalfx-agent/blob/main/docs/monitors/vsphere.md>` in GitHub.
 
 .. list-table::
    :widths: 18 18 18 18
@@ -155,6 +155,7 @@ monitor:
       - No
       - ``string``
       - vSphere username.
+
    - 
 
       - ``password``
@@ -163,6 +164,14 @@ monitor:
       - vSphere password.
    - 
 
+      - ``filter``
+      - No
+      - ``string``
+      - * Limits the inventory traversed by the monitor. Leave blank or omit to traverse and get metrics for the entire vSphere inventory. Otherwise, this expression is evaluated per cluster. If ``true``, metrics are collected for the objects in the cluster, otherwise it's skipped. 
+        * The expression can use the variables ``Datacenter`` and ``Cluster``. For example, to collect metrics for a specific datacenter and cluster, use ``filter: "Datacenter == 'MyDatacenter' && Cluster == 'MyCluster'"``. 
+        * See :new-page:`expr <https://github.com/antonmedv/expr>` in GitHub for advanced syntax.
+   - 
+
       - ``insecureSkipVerify``
       - No
       - ``bool``

infrastructure/monitor/azure.rst

@@ -155,10 +155,6 @@ The Azure integration adds the ``azure_resource_id`` dimension to metrics receiv
 
 The Azure integration truncates the dimension value to 256 bytes, which is the maximum length of a Splunk Observability Cloud dimension value.
 
-If you install collectd on an Azure Compute Virtual Machine instance using the
-:new-page:`standard install script <https://github.com/signalfx/signalfx-collectd-installer>`,
-the installation automatically adds the ``azure_resource_id``.
-
 Azure integration generic dimensions
 --------------------------------------------------------------------------------
 

splunkplatform/centralized-rbac.rst

@@ -108,7 +108,9 @@ To set up centralized user and role management, follow these steps:
 
     .. code-block:: bash
 
-              acs observability enable-centralized-rbac --o11y-access-token <access-token>
+      acs observability enable-centralized-rbac --o11y-access-token <access-token>
+
+.. note:: It takes around 30 minutes for a new role to be available on the :guilabel:`Roles` page. 
 
 How centralized user and role management works
 =================================================================================================