Monitor Azure 🔗

Splunk Observability Cloud can automatically import metrics and metadata from your Microsoft Azure services powered by Azure Monitor.

For a list of supported Azure services in Observability Cloud, refer to Available Azure integrations.
Before you can start monitoring any Microsoft Azure resources, Connect to Azure and send data to Splunk Observability Cloud.
To create filters using the API, see Create filters using the API in the developer portal documentation.
See https://docs.microsoft.com/en-us/azure/azure-monitor/overview on the Microsoft site for more information.

You can also export and monitor data from sources running in your Azure environment, as described in the following table.

Get data in	Monitor	Description
Collect Kubernetes data	Monitor Kubernetes (classic version)	Collect metrics and logs from Kubernetes clusters running in Azure Kubernetes Service.
Collect Linux data Collect Windows data	Monitor hosts	Collect metrics and logs from Linux and Windows hosts running in Virtual Machine instances.
Instrument back-end applications to send spans to Splunk APM	Introduction to Splunk APM	Collect application metrics and spans running in hosts or Kubernetes clusters.

Monitor Azure services and identify problems 🔗

View the health of Azure supported services at a glance from the Infrastructure page. See more details on available content at Use default dashboards and built-in content to monitor Azure services.

You can also drill down into specific instances of an Azure service. For example, view key metrics for the Virtual Machines service, and filter for a specific ID to analyze a particular virtual machine instance.

Follow these steps to analyze problem Azure services from the Infrastructure page:

Select Infrastructure > Microsoft Azure.
Select the specific service you want to analyze. For example, select Virtual Machines to view metrics of a virtual machine. If you see “No Data Found,” you need to first configure an integration.
Compare instances of the service along the following metrics with the Color by drop-down list. In the heat map, colors represent the health of instances based on the metrics you select. For example, a heat map that shows green and red, uses green to denote healthy and red to denote unhealthy instances. If your heat map has multiple colors, then the lighter gradient represents less activity, and the darker gradient represents more activity.

You can color by metrics like CPU utilization and filter by dimensions like geographic region.
Group instances based on metadata about each instance with the Group by drop-down list.

You can group instances according to the region or resource group they are running in or the environment tag. Use this to see correlations between different parts of your infrastructure and its performance.

Find outliers for your metrics with the Find Outliers setting. Specify the Scope and Strategy.

Set the Scope to analyze outliers from across the entire visible population of instances, or only within groups defined by the dimension or property you grouped instances by.

You can select one of two Strategies to find outliers, as described in the following table.

Strategy	Description
`Deviation from Mean`	Instances appear as red that exceed the mean value of the metric by at least three standard deviations. Use this setting to find the most extreme outliers.
`Deviation from Median`	Instances appear as red that exceed the median absolute deviation value by at least three absolute deviations. This setting does not weigh extreme outliers as heavily as the standard deviation.

Select a specific instance you want to investigate further to view all the metadata and key metrics for the instance. For every instance, Observability Cloud provides a default dashboard.

Analyze all the available metadata about the cloud service the instance is running in, the instance itself, and any custom tags associated with the instance. The default dashboard provides metric time series (MTS) for key metrics.

Use default dashboards and built-in content to monitor Azure services 🔗

Observability Cloud provides default dashboards and built-in content for selected Azure services.

Default dashboards 🔗

To see all the pre-built dashboards for data collected in your organization, select Dashboards > Built-in. Supported services include:

Azure App service
Azure batch
Azure Event Hubs
Azure Functions
Azure Kubernetes service
Azure Logic Apps
Azure redis caches
Azure SignalR hubs
Azure SQL databases
Azure SQL server elastic pools
Azure Storage
Azure Virtual Machines
Azure VM Scale Sets

Explore built-in navigators 🔗

To see all of the out-of-the-box navigators provided for data collected in your organization, go to the Infrastructure page. Supported services include:

App services
Azure functions
Batch accounts
Elastic pools
Event hubs
Logic apps
Redis cache
SQL database
Storage
Virtual machines
Dashboards

Content from Azure Virtual Machines 🔗

Azure Virtual Machines instances are powered by their respective public cloud service as well as the Splunk Distribution of OpenTelemetry Collector. You need both for all the charts to display data in the built-in dashboards.

If you have only the public cloud service and the Smart Agent configured, some charts in the built-in dashboards for Azure Virtual Machines instances display no data.
If you have only the public cloud service configured, you can see all the cards representing the services where data come from, but some charts in the built-in dashboards for Azure Virtual Machines instances display no data.
If you have only Smart Agent configured, Azure Virtual Machines instance navigator isn’t available.

Note

The SignalFx Smart Agent has reached End of Support. To use the Collector, see Migrate from SignalFx Smart Agent to the Splunk Distribution of OpenTelemetry Collector.

Identify Azure resources using metadata 🔗

You can use all the Azure metadata imported into Observability Cloud, regardless of the mechanism by which you collect and send metrics. This feature is available for the relevant Azure Services as well as metrics collected by the collectd agent.

Azure metadata helps you analyze metrics by custom tags, region, host names, and other dimensions.

Unsupported characters in tags 🔗

Be careful when choosing tag names: 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.

The azure_resource_id dimension 🔗

The Azure integration adds the azure_resource_id dimension to metrics received from Azure. This value is derived from Azure’s resource_id for the resource, and has the following syntax:

<subscription_id>/<resource_group_name>/<resource_provider_namespace>/<resource_name>

The Azure integration truncates the dimension value to 256 bytes, which is the maximum length of an Observability Cloud dimension value.

If you install collectd on an Azure Compute Virtual Machine instance using the standard install script , the installation automatically adds the azure_resource_id.

Azure integration generic dimensions 🔗

The metric time series (MTS) associated with Azure metrics have the following generic dimensions, common to all services:

Dimension name	Description
`azure_resource_id`	Unique identifier for the Azure object
`resource_group_id`	ID of the resource group the Azure object belongs to
`subscription_id`	ID of the subscription the resource belongs to
`resource_type`	Type of the Azure object
`aggregation_type`	The Azure aggregation type of the metric
`primary_aggregation_type`	Indicates whether or not the aggregation type is the primary type
`unit`	Unit of the metric value

resource_group_id is derived from the Azure resource group id with the following syntax:

<subscription_id>/<resource_group_name>

Some Azure services include dimensions that Observability Cloud adds to MTS. For example, the metrics from Azure Storage provider include the dimensions apiname and geotype.

Azure integration resource metadata 🔗

The Azure integration queries the Azure API to retrieve metadata for monitored resources. You can filter and group MTS by this metadata in charts and in the Infrastructure Navigator.

The Azure integration adds the metadata as custom properties of a specific Azure MTS dimension, as follows:

Metadata for services in a subscription is added as custom properties of the subscription_id dimension. To learn more, see Subscription metadata.
Metadata for services within a resource group is added as custom properties of the resource_group_id dimension. To learn more, see Resource-group metadata.
Metadata that are service-specific is added as properties of the azure_resource_id dimension. To learn more, see Service-level metadata.
Tags on all resources are added to the azure_resource_id dimension. To learn more, see Azure tags for resource groups.

Subscription metadata 🔗

The following table shows the metadata that the Azure integration syncs for services in a subscription:

Azure name	Custom property	Description
`displayName`	`azure_subscription_display_name`	The display name of the subscription. For example, `Pay-As-You-Go`
`state`	`azure_subscription_state`	State of the subscription. For example, `Enabled`

Resource-group metadata 🔗

The following table shows the metadata that the Azure integration syncs for services in a resource group:

Azure name	Custom property	Description
`name`	`azure_resource_group_name`	Name of the resource group
`provisioningState`	`azure_resource_group_provisioning_state`	Provisioning state of the resource group. For example, `Succeeded`
`region`	`azure_resource_group_region`	Region to which the resource group belongs. For example, `eastus`
Tags	`azure_resource_group_tag<name-of-tag>`, if resource group has user-defined tags	All resource group wide tags

Azure tags for resource groups 🔗

Azure tags for resource groups are a list of key:value pairs, and from them the Azure integration creates Observability Cloud tags that have the syntax azure_resource_group_tag<name-of-tag>. For example, if Azure has [key1:label01, key2:label02] as the tags property for a resource group, the Azure integration creates two tags: azure_resource_group_tag_key1 and azure_resource_group_tag_key2.

Service-level metadata 🔗

The following tables shows the metadata that the Azure integration syncs for individual services:

Autoscale settings

For autoscale settings, Observability Cloud syncs the following properties:

Azure name	Custom property	Description
`autoscaleEnabled`	`azure_autoscale_enabled`	Indicates whether automatic scaling is enabled
`targetResourceId`	`azure_target_resource_id`	Resource identifier of the resource that the autoscale settings are added to
`regionName`	`azure_region`	Name of the region the resource is in. For example, `Central US`
`state`	`azure_state`	State of the app. For example, `Running`

Batch accounts

For batch accounts, Observability Cloud syncs the following properties:

Azure name	Custom property	Description
`activeJobAndJobScheduleQuota`	`azure_active_job_and_job_schedule_quota`	Active job and job schedule quota for this batch account
`coreQuota`	`azure_core_quota`	Core quota for the batch account
`poolQuota`	`azure_pool_quota`	Pool quota for the batch account
`provisioningState`	`azure_provisioning_state`	Provisioning state of the batch account. For example, `Succeeded`
`regionName`	`azure_region`	Name of the region the resource is in. For example, `Central US`

Function apps and web apps

For function apps and web apps, Observability Cloud syncs the following properties:

Azure name	Custom property	Description
`availabilityState`	`azure_availabilityState`	Availability state of the app. For example `Normal`
`kind`	`azure_kind`	The type of resource. For example, `app`
`name`	`azure_resource_name`	Name of the function or app
`regionName`	`azure_region`	Name of the region the resource is in. For example, `Central US`
`state`	`azure_state`	State of the app. For example, `Running`

Redis caches

For Redis caches, Observability Cloud syncs the following properties:

Azure name	Custom property	Description
`hostName`	`azure_host_name`	Host name of the Redis cache
`isPremium`	`azure_is_premium`	Indicates whether or not the service is premium
`nonSslPort`	`azure_non_ssl_port`	Indicates whether or not non-SSL port is enabled
`port`	`azure_port`	Port value for Redis cache. For example, `6379`
`provisioningState`	`azure_provisioning_state`	Provisioning state of the Redis cache. For example, `Succeeded`
`redisVersion`	`azure_redis_version`	Version of Redis
`regionName`	`azure_region`	Name of the region the resource is in. For example, `Central US`
`shardCount`	`azure_shard_count`	Number of shards
`sku`	`azure_sku`	SKU of the Redis cache. For example, `Standard_C1`
`sslPort`	`azure_ssl_port`	SSL port value for Redis cache. For example, `6380`

Storage accounts

For storage accounts, Observability Cloud syncs the following properties:

Azure name	Custom property	Description
`creationTime`	`azure_creation_time`	Time at which the account was created. For example, `Thu Jan 19 18:16:25 UTC 2018`
`kind`	`azure_kind`	Kind of storage account. For example, `Storage` or `BLOB`
`regionName`	`azure_region`	Name of the region the resource is in. For example, `Central US`
`sku`	`azure_sku`	SKU of the storage account. For example, `Standard_LRS`

Virtual machines

For virtual machines, Observability Cloud retrieves a subset of metadata about the instance, as well as custom metadata you specify for the instance.

Azure name	Custom property	Description
`computerName`	`azure_computer_name`	Name of the virtual machine instance
`imageReference.offer`	`azure_image_reference_offer`	Offer of the image reference. For example, `UbuntuServer`
`imageReference.publisher`	`azure_image_reference_publisher`	Publisher of the image reference. For example, `Canonical`
`imageReference.sku`	`azure_image_reference_sku`	SKU of the image reference. For example, `16.04-LTS`
`imageReference.version`	`azure_image_reference_version`	Version of the image reference. For example, `latest`
`osDiskCachingType`	`azure_os_disk_caching_type`	OS Disk caching type of the instance. For example, `ReadWrite`
`osType`	`azure_os_type`	Type of OS on the virtual machine. For example, `"LINUX"` or `"WINDOWS"`
`osDiskSize`	`azure_os_disk_size`	Disk size in GB
`powerState`	`azure_power_state`	Power state of the virtual machine. For example, `PowerState/running`
`provisioningState`	`azure_provisioning_state`	Provisioning state of the virtual machine. For example, `Succeeded`
`regionName`	`azure_region`	Name of the region the resource is in. For example, `Central US`
`size`	`azure_size`	Information about the size of the virtual machine. For example, `Standard_D2s_v3`
`vmId`	`azure_vm_id`	ID given to the virtual machine instance by Azure

Virtual machine scale sets

For virtual machine scale sets, Observability Cloud syncs the following properties:

Azure name	Custom property	Description
`capacity`	`azure_capacity`	Number of instances in the scale set
`computerNamePrefix`	`azure_computer_name_prefix`	Computer name prefix of the instances in the scale set
`imageReference.offer`	`azure_image_reference_offer`	Offer of the image reference. For example, `UbuntuServer`
`imageReference.publisher`	`azure_image_reference_publisher`	Publisher of the image reference. For example, `Canonical`
`imageReference.sku`	`azure_image_reference_sku`	SKU of the image reference. For example, `16.04-LTS`
`imageReference.version`	`azure_image_reference_version`	Version of the image reference. For example, `latest`
`osDiskCachingType`	`azure_os_disk_caching_type`	OS Disk caching type of the instance. For example, `ReadWrite`
`overProvisionEnabled`	`azure_over_provision_enabled`	Indicates whether or not over provisioning is enabled
`primaryNetworkId`	`azure_primary_network_id`	ID of the primary network of the scale set
`regionName`	`azure_region`	Name of the region the resource is in. For example, `Central US`
`upgradeModel`	`azure_upgrade_model`	Upgrade model of the scale set. For example, `Manual`

Virtual machines in scale sets

For virtual machines in scale sets, Observability Cloud syncs the following properties:

Azure name	Custom property	Description
`imageReference.offer`	`azure_image_reference_offer`	Offer of the image reference. For example, `UbuntuServer`
`imageReference.publisher`	`azure_image_reference_publisher`	Publisher of the image reference. For example, `Canonical`
`imageReference.sku`	`azure_image_reference_sku`	SKU of the image reference. For example, `16.04-LTS`
`imageReference.version`	`azure_image_reference_version`	Version of the image reference. For example, `latest`
`instanceId`	`azure_instance_id`	Instance ID of the VM in the Scaleset
`osDiskCachingType`	`azure_os_disk_caching_type`	OS Disk caching type of the instance. For example, `ReadWrite`
`osDiskName`	`azure_os_disk_name`	OS Disk name of the instance
`osDiskSize`	`azure_os_disk_size`	OS Disk size of the instance
`osType`	`azure_os_type`	OS Type. For example, `Linux`
`powerState`	`azure_power_state`	Power state of the instance. For example, `PowerState/running`
`regionName`	`azure_region`	Name of the region the resource is in. For example, `Central US`
`size`	`azure_size`	Size of the instance. For example, `Standard_A1`
`sku`	`azure_sku`	SKU of the instance. For example, `com.microsoft.azure.management.compute.Sku@151e5d8d`

Related Topics