title | description | ms.service | ms.topic | ms.custom | ms.date |
---|---|---|---|---|---|
Use Azure Monitor logs to monitor Azure HDInsight clusters |
Learn how to use Azure Monitor logs to monitor jobs running in an HDInsight cluster. |
hdinsight |
how-to |
devx-track-azurepowershell, references_regions, devx-track-azurecli |
05/10/2024 |
Learn how to enable Azure Monitor logs to monitor Hadoop cluster operations in HDInsight. And how to add an HDInsight monitoring solution.
Azure Monitor logs is an Azure Monitor service that monitors your cloud and on-premises environments. The monitoring is to maintain their availability and performance. It collects data generated by resources in your cloud, on-premises environments and from other monitoring tools. The data is used to provide analysis across multiple sources.
[!INCLUDE azure-monitor-log-analytics-rebrand]
If you don't have an Azure subscription, create a free account before you begin.
Important
New Azure Monitor experience is available in all the regions as a preview feature.
-
A Log Analytics workspace. You can think of this workspace as a unique Azure Monitor logs environment with its own data repository, data sources, and solutions. For the instructions, see Create a Log Analytics workspace.
-
An Azure HDInsight cluster. Currently, you can use Azure Monitor logs with the following HDInsight cluster types:
- Hadoop
- HBase
- Interactive Query
- Kafka
- Spark
For the instructions on how to create an HDInsight cluster, see Get started with Azure HDInsight.
-
If using PowerShell, you'll need the Az Module. Ensure you have the latest version. If necessary, run
Update-Module -Name Az
. -
If wanting to use Azure CLI and you haven't yet installed it, see Install the Azure CLI.
Note
New Azure Monitor experience is only available in all the regions as a preview feature. It is recommended to place both the HDInsight cluster and the Log Analytics workspace in the same region for better performance.
In this section, you configure an existing HDInsight Hadoop cluster to use an Azure Log Analytics workspace to monitor jobs, debug logs, and so on.
-
From the Azure portal, select your cluster. The cluster is opened in a new portal page.
-
From the left, under Monitoring, select Monitor Integration.
-
From the main view, under Azure Monitor for HDInsight Clusters Integration, select Enable.
-
From the Select a workspace drop-down list, select an existing Log Analytics workspace.
-
Select Save. It takes a few moments to save the setting.
:::image type="content" source="./media/hdinsight-hadoop-oms-log-analytics-tutorial/hdinsight-enable-azure-monitor.png" alt-text="Enable monitoring for HDInsight clusters.":::
If you want to disable Azure Monitor, you can do the same in this portal.
You can enable Azure Monitor logs using the Azure PowerShell Az module Enable-AzHDInsightAzureMonitor cmdlet.
# Enter user information
$resourceGroup = "<your-resource-group>"
$cluster = "<your-cluster>"
$LAW = "<your-Log-Analytics-workspace>"
# End of user input
# obtain workspace id for defined Log Analytics workspace
$WorkspaceId = (Get-AzOperationalInsightsWorkspace `
-ResourceGroupName $resourceGroup `
-Name $LAW).CustomerId
# obtain primary key for defined Log Analytics workspace
$PrimaryKey = (Get-AzOperationalInsightsWorkspace `
-ResourceGroupName $resourceGroup `
-Name $LAW | Get-AzOperationalInsightsWorkspaceSharedKeys).PrimarySharedKey
# Enables monitoring and relevant logs will be sent to the specified workspace.
Enable-AzHDInsightAzureMonitor `
-ResourceGroupName $resourceGroup `
-ClusterName $cluster `
-WorkspaceId $WorkspaceId `
-PrimaryKey $PrimaryKey
# Gets the status of monitoring installation on the cluster.
Get-AzHDInsightAzureMonitor `
-ResourceGroupName $resourceGroup `
-ClusterName $cluster
To disable, the use the Disable-AzHDInsightAzureMonitor cmdlet:
Disable-AzHDInsightAzureMonitor -ResourceGroupName $resourceGroup `
-ClusterName $cluster
You can enable Azure Monitor logs using the Azure CLI az hdinsight azure-monitor enable
command.
# set variables
export resourceGroup=RESOURCEGROUPNAME
export cluster=CLUSTERNAME
export LAW=LOGANALYTICSWORKSPACENAME
# Enable the Azure Monitor logs integration on an HDInsight cluster.
az hdinsight azure-monitor enable --name $cluster --resource-group $resourceGroup --workspace $LAW
# Get the status of Azure Monitor logs integration on an HDInsight cluster.
az hdinsight azure-monitor show --name $cluster --resource-group $resourceGroup
To disable, the use the az hdinsight monitor disable
command.
az hdinsight azure-monitor disable --name $cluster --resource-group $resourceGroup
HDInsight provides workload-specific workbook to help you quickly get insights. This workbook collects important performance metrics from your HDInsight cluster and provides the visualizations and dashboards for most common scenarios. The out-of-box insights give a complete view of a single HDInsight cluster including resource utilization and application status.
Available HDInsight workbooks:
- HDInsight Spark Workbook
- HDInsight Kafka Workbook
- HDInsight HBase Workbook
- HDInsight Hive/LLAP Workbook
Screenshot of Spark Workbook :::image type="content" source="./media/hdinsight-hadoop-oms-log-analytics-tutorial/hdinsight-spark-workbook.png" alt-text="Spark workbook screenshot.":::
Azure monitor supports collecting and analyzing performance metrics for the nodes in your cluster. For more information, see Linux performance data sources in Azure Monitor.
HDInsight support cluster auditing with Azure Monitor logs, by importing the following types of logs:
log_gateway_audit_CL
- this table provides audit logs from cluster gateway nodes that show successful and failed sign-in attempts.log_auth_CL
- this table provides SSH logs with successful and failed sign-in attempts.log_ambari_audit_CL
- this table provides audit logs from Ambari.log_ranger_audti_CL
- this table provides audit logs from Apache Ranger on ESP clusters.
-
A Log Analytics workspace. You can think of this workspace as a unique Azure Monitor logs environment with its own data repository, data sources, and solutions. For the instructions, see Create a Log Analytics workspace.
-
If you intend to use Azure Monitor integration on a cluster behind a firewall, complete the Prerequisites for clusters behind a firewall.
-
An Azure HDInsight cluster. Currently, you can use Azure Monitor logs with the following HDInsight cluster types:
- Hadoop
- HBase
- Interactive Query
- Kafka
- Spark
For the instructions on how to create an HDInsight cluster, see Get started with Azure HDInsight.
-
If using PowerShell, you'll need the Az Module. Ensure you have the latest version. If necessary, run
Update-Module -Name Az
. -
If wanting to use Azure CLI and you haven't yet installed it, see Install the Azure CLI.
Note
It is recommended to place both the HDInsight cluster and the Log Analytics workspace in the same region for better performance. Azure Monitor logs is not available in all Azure regions.
In this section, you configure an existing HDInsight Hadoop cluster to use an Azure Log Analytics workspace to monitor jobs, debug logs, and so on.
-
From the Azure portal, select your cluster. The cluster is opened in a new portal page.
-
From the left, under Monitoring, select Azure Monitor.
-
From the main view, under Azure Monitor Integration, select Enable.
-
From the Select a workspace drop-down list, select an existing Log Analytics workspace.
-
Select Save. It takes a few moments to save the setting.
:::image type="content" source="./media/hdinsight-hadoop-oms-log-analytics-tutorial/azure-portal-monitoring.png" alt-text="Enable monitoring for HDInsight clusters.":::
You can enable Azure Monitor logs using the Azure PowerShell Az module Enable-AzHDInsightMonitoring cmdlet.
# Enter user information
$resourceGroup = "<your-resource-group>"
$cluster = "<your-cluster>"
$LAW = "<your-Log-Analytics-workspace>"
# End of user input
# obtain workspace id for defined Log Analytics workspace
$WorkspaceId = (Get-AzOperationalInsightsWorkspace `
-ResourceGroupName $resourceGroup `
-Name $LAW).ResourceId
# obtain primary key for defined Log Analytics workspace
$PrimaryKey = (Get-AzOperationalInsightsWorkspace `
-ResourceGroupName $resourceGroup `
-Name $LAW | Get-AzOperationalInsightsWorkspaceSharedKeys).PrimarySharedKey
# Enables monitoring and relevant logs will be sent to the specified workspace.
Enable-AzHDInsightMonitoring `
-ResourceGroupName $resourceGroup `
-Name $cluster `
-WorkspaceId $WorkspaceId `
-PrimaryKey $PrimaryKey
# Gets the status of monitoring installation on the cluster.
Get-AzHDInsightMonitoring `
-ResourceGroupName $resourceGroup `
-Name $cluster
To disable, the use the Disable-AzHDInsightMonitoring cmdlet:
Disable-AzHDInsightMonitoring -Name "<your-cluster>"
You can enable Azure Monitor logs using the Azure CLI [az hdinsight monitor enable
](/cli/azure/hdinsight/monitor#az-hdinsight-monitor-enable) command.
# set variables
export resourceGroup=RESOURCEGROUPNAME
export cluster=CLUSTERNAME
export LAW=LOGANALYTICSWORKSPACENAME
# Enable the Azure Monitor logs integration on an HDInsight cluster.
az hdinsight monitor enable --name $cluster --resource-group $resourceGroup --workspace $LAW
# Get the status of Azure Monitor logs integration on an HDInsight cluster.
az hdinsight monitor show --name $cluster --resource-group $resourceGroup
To disable, the use the az hdinsight monitor disable
command.
az hdinsight monitor disable --name $cluster --resource-group $resourceGroup
To be able to successfully set up Azure Monitor integration with HDInsight, behind a firewall, some customers may need to enable the following endpoints:
Agent Resource | Ports | Direction | Bypass HTTPS inspection |
---|---|---|---|
*.ods.opinsights.azure.com | Port 443 | Outbound | Yes |
*.oms.opinsights.azure.com | Port 443 | Outbound | Yes |
*.azure-automation.net | Port 443 | Outbound | Yes |
If you have security restrictions related to enabling wildcard storage endpoints, there is an alternate option. You can do the following instead:
- Create a dedicated storage account
- Configure the dedicated storage account on their log analytics workspace
- Enable that dedicated storage account in their firewall
Once the setup is successful, enabling necessary endpoints for data ingestion is important. It is recommended that you enable the *.blob.core.windows.net endpoint for data ingestion to succeed.
HDInsight provides cluster-specific management solutions that you can add for Azure Monitor Logs. Management solutions add functionality to Azure Monitor Logs, providing more data and analysis tools. These solutions collect important performance metrics from your HDInsight clusters. And provide the tools to search the metrics. These solutions also provide visualizations and dashboards for most cluster types supported in HDInsight. By using the metrics that you collect with the solution, you can create custom monitoring rules and alerts.
Available HDInsight solutions:
- HDInsight Hadoop Monitoring
- HDInsight HBase Monitoring
- HDInsight Interactive Query Monitoring
- HDInsight Kafka Monitoring
- HDInsight Spark Monitoring
For management solution instructions, see Management solutions in Azure. To experiment, install a HDInsight Hadoop Monitoring solution. When it's done, you see an HDInsightHadoop tile listed under Summary. Select the HDInsightHadoop tile. The HDInsightHadoop solution looks like:
:::image type="content" source="media/hdinsight-hadoop-oms-log-analytics-tutorial/hdinsight-oms-hdinsight-hadoop-monitoring-solution.png" alt-text="HDInsight monitoring solution view.":::
Because the cluster is a brand new cluster, the report doesn't show any activities.
HDInsight support cluster auditing with Azure Monitor logs, by importing the following types of logs:
log_gateway_audit_CL
- this table provides audit logs from cluster gateway nodes that show successful and failed sign-in attempts.log_auth_CL
- this table provides SSH logs with successful and failed sign-in attempts.log_ambari_audit_CL
- this table provides audit logs from Ambari.log_ranger_audti_CL
- this table provides audit logs from Apache Ranger on ESP clusters.
When Azure Monitor integration is enabled on a cluster, the Log Analytics agent, or Operations Management Suite (OMS) Agent, is installed on the cluster and is not updated unless you disable and re-enable Azure Monitor Integration. Complete the following steps if you need to update the OMS Agent on the cluster. If you are behind a firewall you may need to complete the Prerequisites for clusters behind a firewall before completing these steps.
- From the Azure portal, select your cluster. The cluster is opened in a new portal page.
- From the left, under Monitoring, select Azure Monitor.
- Note the name of your current Log Analytics workspace.
- From the main view, under Azure Monitor Integration, disable the toggle, and then select Save.
- After the setting saves, re-enable the Azure Monitor Integration toggle, and ensure the same Log Analytics workspace is selected, and then select Save.
If you have Azure Monitor Integration enabled on a cluster, updating the OMS agent will also update the Open Management Infrastructure (OMI) version. You can check the OMI version on the cluster by running the following command:
sudo /opt/omi/bin/omiserver –version