Azure Linux VMs Monitoring

Setup Azure Log Analytics

This Opspack utilises Azure Log Analytics to collect data directly from your Azure Virtual Machines. To enable Azure Log Analytics follow the steps outlined below. If you already have an Azure Workspace, you can skip Step 1.

Step 1: Create a Workspace

In the Azure portal, click All Services and filter for Log Analytics workspaces. Select Log Analytics workspaces.

Click Create, and then fill in the fields as described:

• Select a Subscription from the drop-down list.
• Select an existing Resource Group or create a new one.
• Provide a Name such as DefaultWorkspace.
• Select the Region your VMs are deployed to.
• Optionally, you can click Next : Pricing tier to select the Pricing Tier you use.

After providing the required fields click Review + Create and then Create.

From the list of Log Analytics workspaces, select the workspace you just created.

From the left-hand menu, select Overview.

Make a note of the Workspace ID as this will be required when configuring the Opspack.

Step 2: Enable the Log Analytics VM Extension

Log Analytics can be enabled on existing Azure Linux and Windows VMs using the Log Analytics agent.

In the Azure portal, click All Services and filter for Log Analytics workspaces. Select Log Analytics workspaces.

From the list of Log Analytics workspaces, select the workspace you created earlier.

From the left-hand menu, under Workspace Data Sources, select Virtual Machines.

From the list of virtual machines, select the virtual machine you wish to install the agent on. Notice that the Log Analytics Connection for the VM indicates that it is Not connected.

Select the virtual machine and then click Connect. The agent will be installed and configured for your Log Analytics workspace. Please note, this process may take a few minutes to complete.

After the agent has been installed and connected, the Log Analytics Connection will be updated to This workspace.

Step 3: Collect performance data

In the Azure portal, click All Services and filter for Log Analytics workspaces. Select Log Analytics workspaces.

From the list of Log Analytics workspaces, select the workspace you created earlier.

From the workspace's left menu, select Agents configuration.

Select Linux Performance Counters.

Enable the following performance counters, by clicking + Add performance counter, then searching for and selecting them from the dropdown list:

• Logical Disk\Free Megabytes
• Logical Disk\% Used Space
• Memory\Available MBytes Memory
• Memory\% Used Memory
• Memory\% Used Swap Space
• Processor\% Processor Time
• Processor\% Privileged Time
• System\Uptime

Ensure each Instance field contains an asterisk * as shown.

After adding the required performance counters, click Apply to save the configuration.

Then select the Syslog tab.

Enable the following facilities, by clicking + Add facility, then searching for and selecting them from the dropdown list:

• syslog
• kern
• authpriv
• daemon

Make sure all checkboxes under Emergency, Alert, Critical, Error, Warning, Notice, Info, Debug are ticked as shown.

Finally, select the Storage Account Logs option under your workspace, and add the storage account related to your Virtual Machine.

Verify Log Analytics Agent is running correctly (optional)

To verify the agent is connected and operating correctly, run the following command on your Azure VM.

/opt/microsoft/omsagent/bin/omsadmin.sh -l

It should return a status similar to:

Primary Workspace: <workspaceId> Status: Onboarded(OMSAgent Running)

If the Agent is not connected to a workspace, connect it to your chosen workspace using the following command.

/opt/microsoft/omsagent/bin/omsadmin.sh -w <workspace id> -s <shared key> [-d <top level domain>]

If the agent is connected but not running, restart the agent using the following command.

sudo /opt/microsoft/omsagent/bin/service_control restart

Finally, verify the agent is operating correctly by running the following command again.

/opt/microsoft/omsagent/bin/omsadmin.sh -l

Usage Instructions

To use this Host Template you will need to provide access to the subscription you wish to monitor

Navigate to the Subscriptions section and select your Subscription.

In the Subscription to be monitored, click Access Control (IAM).

Then click the Add button, select the required role and select the application, once for each of the following roles:

• Reader

Repeat these steps for each subscription you wish to monitor.

Step 1: Add this Host Template

Add the Cloud - Azure - Linux VMs Host Template to your Opsview Monitor host. If the resource you're monitoring has no hostname or public IP, then open the Advanced settings pane and change Host Check Command to Always assumed to be UP.

For more information, refer to Opsview Knowledge Center - Adding Host Templates to Hosts.

Step 2: Add and configure variables required for this Host Template

The Service Checks in this Host Template use the following variables, and they will be added to your Opsview Monitor instance when you import the Opspack:

AZURE_CREDENTIALS

The Value is not used and therefore can be set to anything. Override the arguments with your Azure Credentials.

AZURE_RESOURCE_DETAILS

The Value is not used and therefore can be set to anything. Override the arguments with your Azure Resource Details.

AZURE_LOG_ANALYTICS_DETAILS

The Value is not used and therefore can be set to anything. Override the arguments with your Log Analytics Details.

AZURE_COMPUTER_NAME

Set this value to the hostname of the Azure VM you want to monitor if it is different from the resource name. If your VM has been joined to a domain you will need to specify the FQDN.

For more information, refer to Opsview Knowledge Center - Adding Variables to Hosts.

For mode-specific help, run the plugin with the -h -m <mode> flags. This will list the required and optional Variable Arguments for that mode. The appropriate mode for each Service Check is listed here:

Step 3: Apply changes and the system will now be monitored