| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nIntegration Name\n\n | \n\nUnique name of this integration. For example: My Azure Log Analytics integration. This field is required.**Note:** When you fill in this field, the generic name displayed on the form adjusts automatically to match the name you entered.\n\n |
| \n\nExecute on\n\n | \n\nOption to select whether to use a specific MID Server or a MID Server cluster. This field is required.\n\n |
| \n\nMID server name\n\n | \n\n\\(Only when the **Execute on** field is set to Specific MID Server\\)\n\n MID Server to which log data from Microsoft Azure Log Analytics is pulled. This field is required.**Note:**\n\n- You can select only MID Servers that support basic authentication. MID Servers that support mTLS are not listed.\n- The default maximum number of integrations streaming logs to a single MID Server is 10. You can modify this number in the MID Server properties.\n- If log ingestion is not enabled for the selected MID Server, Health Log Analytics enables it automatically.\n\n |
| \n\nMID MID Server Cluster\n\n | \n\n\\(Only when **Execute on** is set to Specific MID Server cluster.\\)\n\nThe MID Server cluster to which the log data is pulled. This field is required.The data input runs on a single MID Server in the cluster until that MID Server fails. The system then moves all the data input tasks to the next available MID Server in the cluster according to the configured order.\n\n**Note:**\n\n- Health Log Analytics supports only failover MID Server clusters. In these clusters, multiple MID Servers are grouped together for failover protection. When selecting a cluster from the data input or integration form, the MID Server clusters list displays only failover clusters.\n- Log ingestion must be enabled for each MID Server in the cluster. If log ingestion is not enabled for the active MID Server, Health Log Analytics enables it automatically.\n- The default maximum number of data inputs or integrations streaming logs to a single MID Server is 10. A cluster passes capacity validation if it contains at least one MID Server with fewer than 10 data inputs or integrations running on it. This is true even when that MID Server is down.\n\nFor more information about MID Server clusters, see [Configure a MID Server cluster](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_ConfigureAMIDServerCluster.md).\n\n |
| \n\nService instance\n\n | \n\nThe service instance \\(formerly the application service\\) to which to bind the log data. This field is required.\n\n |
| \n\nData source\n\n | \n\nThe source of the log data that the integration pulls to your ServiceNow instance: Azure Log Analytics. This field is read-only.\n\n |
| \n\nDescription\n\n | \n\nOption to add a brief description of the integration to help identify it.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nRedirect url\n\n | \n\nThe redirect URL of the access log application. This field is required. The URL refers to the Microsoft Azure redirect\\_uri authorization property. For more information, see the Authorization code URL \\(GET request\\) section in the [Microsoft Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/access-api).\n\n |
| \n\nAuthentication method\n\n | \n\nThe credentials used to access Microsoft Azure resources. This field is required.If no credentials exist, select **Create new Azure Service Principal credential**. Create a credential by filling in the fields and then selecting **Submit**. For information on the **Tenant ID**, **Client ID**, and **Secret key** fields, refer to the [Microsoft Azure documentation](https://learn.microsoft.com/en-us/azure/?product=popular). When you have created a credential, you can select it from the drop-down list.\n\n |
| \n\nWorkspace ID\n\n | \n\nThe Customer ID used to call the Microsoft Azure Log Analytics REST API. This field is required.\n\n |
| \n\nTable name\n\n | \n\nThe name of the table in Microsoft Azure Log Analytics where the data input fetches the log data. For more information, see the View table information section in the [Microsoft Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/log-analytics-tutorial). This field is required.\n\n |
| \n\nEvent time property name\n\n | \n\nThe Microsoft Azure Log Analytics field in which to detect the event time. This field is required.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nEvent Processor workers\n\n | \n\nThe number of concurrent event processing workers, where each worker processes a batch of events independently.\n\n |
| \n\nWorkers queue size\n\n | \n\nThe queue size of the Event Processor workers.\n\n |
| \n\nSub sample drop ratio\n\n | \n\nThe number of events to batch together, out of which one will be discarded. This setting is used to reduce the number of fetched events.\n\n |
| \n\nSub sample receive ratio\n\n | \n\nThe number of events to batch together, out of which all but one will be discarded. This setting is used to decrease the number of received events.\n\n |
| \n\nMax documents per query\n\n | \n\nThe highest number of rows retrieved in each query.\n\n |
| \n\nColumns to select\n\n | \n\nComma-separated list of column names to return.**Note:** This field is ignored when you provide a custom query.\n\n |
| \n\nCharacter encoding\n\n | \n\nThe character encoding for this data input.\n\n |
| \n\nSleep interval \\(seconds\\)\n\n | \n\nThe interval, in seconds, to wait before querying again after a query has returned no events.\n\n |
| \n\nPolling interval\n\n | \n\nThe interval, in seconds, to wait before polling for new events.\n\n |
| \n\nDrop if queue is full\n\n | \n\nOption to discard logs if there is a load on the MID Server.\n\n |
| \n\nLog Query\n\n | \n\nOption to define your own Log Analytics query. This field overrides the values configured in the other query settings fields.**Note:** If this field is empty, Health Log Analytics generates the query using the values set in the other fields.\n\nFor your custom query, use the following JSON format:\n\n`{\"query\": \"query | where TimeGenerated > %s | take 500\"}`\n\nFor example:\n\n```\n{\n\"query\":\"ContainerLog\n | where LogEntry contains 'cartservice'\n | where TimeGenerated > %s\n | take 500\",\n\"workspaces\": [\"defaultworkspace-3ab145ff-f9cd-433f-8533-d1b1ee24aee6-eus\"],\n\"project\": [\"TimeGenerated\", \"LogEntry\", \"LogEntrySource\"]\n}\n```\n\n |