Merge pull request #2080 from splunk/urbiz-OD6177-azure-ui

[6177]: New Azure UI

Author: aurbiztondo-splunk

gdi/get-data-in/connect/azure/azure-connect.rst

@@ -0,0 +1,118 @@
+.. _azure-connect:
+
+**************************************************************
+Connect to Azure: Guided setup and other options 
+**************************************************************
+
+.. meta::
+  :description: Connect your Microsoft Azure account to Splunk Observability Cloud: UI, API
+
+.. toctree::
+  :hidden:
+
+For a list of supported Azure services, see :ref:`azure-integrations`.
+
+.. note:: Splunk is not responsible for data availability, and it can take up to several minutes (or longer, depending on your configuration) from the time you connect until you start seeing valid data from your account. 
+
+.. _connect-to-azure:
+.. _azure-connect-ui:
+
+Connect to Azure with the guided setup
+============================================
+
+From Splunk Observability Cloud, connect to Azure using the :new-page:`Microsoft Azure guided setup <https://login.signalfx.com/#/integrations/azure>`. 
+
+Alternatively, you can navigate to the guided setup on your own:
+
+  #. In the navigation menu, select :menuselection:`Data Management`. 
+  
+  #. Go to the :guilabel:`Available integrations` tab, or select :guilabel:`Add Integration` in the :guilabel:`Deployed integrations` tab.
+
+  #. In the integration filter menu, go to :guilabel:`By Use Case`, and select the :guilabel:`Monitor Infrastructure` use case.
+
+  #. Select the :guilabel:`Microsoft Azure` tile to open the Microsoft Azure guided setup.
+
+  #. To start configuring the connection to Azure, select :guilabel:`New Integration`.
+
+Next, fill in the fields as prompted by the guided setup.
+
+1. Define your Azure connection
+--------------------------------------------------------------------------------------
+
+Complete the following parameters for your integration:
+
+* Select your Azure environment: 
+  
+  * :guilabel:`Azure Government` for an Azure Government instance.
+  
+  * :guilabel:`Azure` for all other Azure connections.
+
+* Select the rate, in seconds, at which you want Splunk Observability Cloud to poll Azure for metric data, with 60 seconds (default) as the minimum unit, and 600 seconds (10 minutes) as the maximum unit.
+
+* Select if you want to import metrics and/or metadata.
+
+* Prepare your Azure account. See :ref:`azure-prereqs`.
+
+2. Establish your Azure connection
+--------------------------------------------------------------------------------------
+
+To create the integration, enter the following information:
+
+* :guilabel:`Name`: Unique name for this connection to Azure. The name field helps you create multiple connections to Azure, each with its own name.
+
+* :guilabel:`Directory ID`: Azure Directory ID you saved in a previous step.
+
+* :guilabel:`App ID`: The Azure app (client) ID you saved in a previous step.
+
+* :guilabel:`Client Secret`: The client secret (password) you saved in a previous step.
+
+3. Select the data to import
+--------------------------------------------------------------------------------------
+
+Choose the data you want to send to Splunk Observability Cloud:
+
+* Select the subscriptions you want to monitor.
+
+* Optional: Select the services you want to monitor. By default, all services supported by Splunk Observability Cloud are selected. Use the pop-up menu to narrow down to specific services. For a list of supported Azure services, see :ref:`azure-integrations`.
+
+* Optional: Add any additional Azure resources or services you want to monitor that are not fully supported by Splunk Observability Cloud. If you add the same resource type to both services and additional services, Splunk Observability Cloud ignores the duplication.
+
+  * Any resource type you specify as an additional service must meet the following criteria:
+
+    * The resource is an Azure generic resource. For resource types that have hierarchical structure, only the root resource type is a generic resource. For example, a Storage Account type can have a File Service type, and a File Service type can have a File Storage type. In this case, only Storage Account is a generic resource.
+
+    * The resource stores its metrics in Azure Monitor. To learn more about Azure Monitor, refer to the Microsoft Azure documentation.
+
+* Optional: Use the :guilabel:`Add Tag` button to create a tag if you want to monitor only tagged data sources, filling out the ``tag name`` and ``tag value`` fields separately to create a tag pair. When tagging, Splunk Observability Cloud only allows alphanumeric characters, and the underscore and minus symbols. Unsupported characters include ``.``, ``:``, ``/``, ``=``, ``+``, ``@``, and spaces, which are replaced by the underscore character. 
+
+.. _connect-azure-other:
+
+Alternatives to connect to Azure
+============================================
+
+.. _connect-to-azure-using-API:
+
+Connect to Azure using the Splunk Observability Cloud API
+--------------------------------------------------------------------------------------
+
+You can use the Splunk API to integrate Azure with Splunk Observability Cloud. For instructions on how to connect to Azure through the API, see :new-page:`Integrate Microsoft Azure monitoring with Splunk Observability Cloud <https://dev.splunk.com/observability/docs/integrations/msazure_integration_overview/>` in the Splunk developer documentation.
+
+Azure tag filtering configured through the UI applies an ``OR`` operator to the ``name:value`` pairs that you specify in separate fields. Values for ``tag name`` and ``tag value`` are what you anticipate for monitored data sources. To apply more complex rules not governed exclusively by the OR operator, connect to Azure through the Splunk Observability Cloud API and modify the contents of the ``resourceFilterRules`` field there.
+
+.. _connect-azure-terraform:
+    
+Connect to Azure using Terraform
+-------------------------------------------
+
+To connect using Terraform, see :ref:`terraform-config`.
+
+Next steps
+============================================
+
+After you connect your Azure account to Splunk Observability Cloud, you can do the following:
+
+* Import Azure metrics, traces, and metadata. For details about the metrics provided by an Azure integration, see :ref:`azure-metrics`.
+* Learn about Splunk Observability Cloud's :ref:`Azure Infrastructure Monitoring options <infrastructure-azure>`. 
+* Use Splunk Observability Cloud tools to monitor your Azure services, such as :ref:`navigators <use-navigators-imm>` and :ref:`dashboards <azure-dashboards>`.
+* Filter Azure monitoring results using tags or dimensions such as ``region`` and ``host name``. 
+* To send logs from Azure to Splunk, see :ref:`ingest-azure-log-data`.

gdi/get-data-in/connect/azure/azure-metrics.rst

@@ -10,9 +10,9 @@ Azure metrics in Splunk Observability Cloud
 
 All available metrics are included by default in any Azure integration with Splunk Observability Cloud.
 
-Metric names and descriptions are generated dynamically from the :strong:`Supported metrics with Azure Monitor` page maintained by Microsoft. See all details in :new-page:`https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/metrics-supported`.
+Metric names and descriptions are generated dynamically from data provided by Microsoft. See all details in Microsoft's :new-page:`Supported metrics with Azure Monitor <https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/metrics-supported>`.
 
-Every metric can either be a counter or a gauge, depending on what dimension is being looked at. If the MTS contains the dimension ``aggregation_type: total`` or ``aggregation_type: count``, then it is sent as a counter. Otherwise, it is sent as a gauge. To learn more, see :ref:`metric-time-series`. 
+Every metric can either be a counter or a gauge, depending on what dimension is being looked at. If the MTS contains the dimension ``aggregation_type: total`` or ``aggregation_type: count``, then it is sent as a counter. Otherwise, it is sent as a gauge. To learn more, see :ref:`metric-types` and :ref:`metric-time-series`. 
 
 Organization metrics
 =================================

gdi/get-data-in/connect/azure/azure-prereqs.rst

@@ -0,0 +1,77 @@
+.. _azure-prereqs:
+.. _azure-integration-prereqs:
+
+*******************************************************************
+Azure authentication, permissions, and supported regions 
+*******************************************************************
+
+.. meta::
+   :description: These are the metrics available for the Azure integration with Splunk Observability Cloud, grouped according to Azure resource.
+
+Successful integration requires administrator privileges for the following:
+
+- Your organization in Splunk Observability Cloud.
+- Creating a new Microsoft Entra ID (formerly Azure Active Directory) application.
+
+To learn more about these privileges, see the Azure documentation for registering a new app.
+
+.. note:: Splunk Observability Cloud supports all Azure regular regions, and Azure Government.
+
+.. _prep-azure-integration:
+
+Prepare Azure for the integration
+============================================
+
+To prepare Microsoft Azure to connect with Splunk Observability Cloud: 
+
+#. Create a Microsoft Entra ID (formerly Azure Active Directory) application.
+#. Specify subscriptions and set subscription permissions.
+
+.. note:: You need to prepare your Microsoft Account in the Azure console. The following sections summarize the steps you need to follow. For more details, refer to the official Azure documentation.
+
+.. _prep-ms-app:
+
+Create a Microsoft Entra ID (formerly Azure Active Directory) application
+--------------------------------------------------------------------------------------
+
+Follow these steps to create a new Microsoft Entra ID application:
+
+#. In your Azure portal, navigate to :menuselection:`Microsoft Entra ID`, and register your new app. Splunk Observability Cloud does not use this information, but you need to provide it in order to create an app on Azure.
+
+#. The Azure portal displays a summary about the application. Save the following information to use when you create your Azure integration in Splunk Observability Cloud:
+      
+  * :guilabel:`Directory (tenant) ID`
+  * :guilabel:`Application (client) ID`
+
+#. Select :guilabel:`Certificates & secrets`. The Certificate is your public key, and the client secret is your password.
+
+#. Create a client secret by providing a description and setting the duration to the longest possible interval, and :guilabel:`Save`. Remember the client secret, you'll need it to create your Azure integration in Splunk Observability Cloud.
+
+.. _prep-ms-subs:
+
+Specify subscriptions and set subscription permissions
+--------------------------------------------------------------------------------------
+
+Set your subscription permissions:
+
+#. In the Azure portal, look for your :guilabel:`Subscriptions`.
+
+#. Find a subscription you want to monitor, and navigate to :menuselection:`Access control (IAM)`.
+
+#. Select :menuselection:`Add`, then select :menuselection:`Add role assignment`.
+
+#. On the :guilabel:`Add role assignment page`, perform the following steps:
+
+   * From the :guilabel:`Role` drop-down list, select the :menuselection:`Monitoring Reader` role.
+   * Leave the :guilabel:`Assign access to` drop-down list unchanged.
+   * Go to :guilabel:`Select member`. In the :guilabel:`Select` text box, start entering the name of the Azure application you just created. The Azure portal automatically suggests names as you type. Enter the application name, and :guilabel:`Save`.
+
+.. note:: Repeat these steps for each subscription you want to monitor.
+
+Connect and send your Azure data
+============================================
+
+After setting up your account proceed to:
+
+* :ref:`azure-connect` 
+* :ref:`azure-logs`