Set up a Microsoft Azure Event Hubs (MID-less) integration for Health Log Analytics

Set up an integration for streaming events from Microsoft Azure Event Hubs to your ServiceNow instance without a MID Server.

Avant de commencer

Role required: evt_mgmt_admin

Pourquoi et quand exécuter cette tâche

This Microsoft Azure Event Hubs integration eliminates the need for a MID Server, which simplifies setup and enables more efficient log data ingestion into your instance. By removing the MID Server requirement, log data collection and processing are streamlined to promote faster analysis and root cause identification.

You set up integrations through the Integrations Launchpad in Service Operations Workspace, which you access from the ITOM AIOps configuration center. The AIOps configuration center is a centralized workspace for configuring and managing AIOps features from a single place. The integrations setup process reduces implementation time compared to manual data input setup in the classic interface in Health Log Analytics. For more information, see Integrations Launchpad in Service Operations Workspace for ITOM.

Procédure

1. Navigate to Workspaces > Service Operations Workspace.
2. From the bottom of the navigation pane, select the AIOps configuration center icon .
   The ITOM AIOps configuration center page appears. The configuration center is a centralized workspace. Use it to configure and manage AIOps features from a single place.
3. From the Integrate section, under Integrations, select Add integration.
   The Integrations Launchpad appears.
4. In the Browse integrations tab, enter Azure Event Hubs (MID-less) in the search field.
5. Select the Azure Event Hubs (MID-less) integration tile.
   Remarque :

   If you start an integration setup before meeting all prerequisites, a message appears. You can cancel the setup and complete the prior requirements first. Alternatively, you can continue in draft mode and complete the requirements later. Note that you can't activate the integration until you have completed all the prerequisites.
6. On the Provide details form, fill in the fields and then select Next.

   Tableau 1. Provide details

   Field	Description
   Integration Name	Unique name of this integration. For example: My Event Hubs MID-less integration. This field is required. Remarque : When you fill in this field, the generic name displayed on the form adjusts automatically to match the name you entered.
   Description	Option to add a brief description of the integration to help identify it.
   Transport	Protocol used to stream the log data. This field is read-only. This integration uses Microsoft Azure Event Hubs to stream log data to your instance.

7. On the Set-up instruction screen, perform the appropriate procedure to install the integration in your third-party console.
   • Install the integration with Bicep, a domain-specific language (DSL) that uses declarative syntax to deploy Azure resources.

     Using Bicep enables automation and consistency across environments through Infrastructure as Code (IaC), allowing you to manage your Azure environment more efficiently. It also supports version control and integration with CI/CD pipelines.

   • Install the integration in the Azure portal.

     If you're doing a one-time setup or prefer a graphical interface, installing in the Azure portal is a good choice. It provides a convenient way to configure resources, making it suitable for straightforward deployments.

   The screen provides a link to detailed configuration instructions for each of these two installation options.
8. Do one of the following:
   • If you completed all the prerequisites before starting the configuration, activate the integration either with or without AI-powered capabilities. Select the appropriate option:
     • Activate with AI enables AI-powered automatic mapping of log data. When the integration is activated successfully, the Overview tab is displayed and Now Assist collects and analyzes log data. An AI icon indicates that Now Assist auto-maps log data to service instances and components for contextual alert generation.
     • Activate activates the integration without AI-powered mapping. The integration is activated and the Overview tab is displayed.
   • If you didn't complete all the prior requirements, select Save draft.

     The system saves the integration as a draft in the Integrations Launchpad Installed integrations tab, under Waiting for your action. You can complete the prerequisites and activate the installation later. For more information, Activate a draft integration in Health Log Analytics.

Que faire ensuite

On the Overview tab, do the following:

• Use the displayed information to refine how Health Log Analytics reads the log data. For more information, see Review log streaming data and adjust integration settings in Health Log Analytics.
• Use the More options menu () to open the Data Input Mapping, Source Type Structures, or Log Sources pages with context from the integration. If your log data is not properly mapped, structured, or sourced, go back and adjust the configuration. If the Service Operations Workspace Log Analytics application is installed, the More options menu also provides direct access to the Log Viewer. Use the Log Viewer to review raw log messages ingested by the integration. For more information, see:
  • Log data auto-mapping and mapping
  • Source type structure adjustment
  • Review logs on the Log Viewer

If you activated the integration with AI, verify that AI correctly auto-mapped log data to service instances and components. To do this, select View mapping under Log context mapping. You can override the AI mapping by selecting a different log field from each list. For more information, see Map logs to service instances, components, and source types for contextual alerts in Health Log Analytics.