For information about the other supported Azure services, see our Azure docs.
Azure SQL Elastic Pool sensor can be disabled and it can be filtered by tags and resource groups. It is possible to configure Azure SQL Elastic Pool sensor via agent configuration in
com.instana.plugin.azure.sqlelasticpool: # Valid values: true, false enabled: false # enabled (true) by default # Comma separated list of tags in key:value format include_tags: # Comma separated list of tags in key:value format exclude_tags: # Comma separated list of resource groups include_resource_groups: # Comma separated list of resource groups exclude_resource_groups:
Azure SQL Elastic Pool sensor can be disabled. To disable monitoring of the Azure SQL Elastic Pool services use the folowing configuration:
com.instana.plugin.azure.sqlelasticpool: enabled: false
Multiple tags and resource groups can be defined, separated by a comma. Tags should be provided as a key-value pair separated by
:. In order to make configuration easier, it is possible to define which tags and resource groups you want to include in discovery or exclude from discovery. In case of defining tag or resource group in both lists (include and exclude), exclude list has higher priority. If there is no need for services filtering, the configuration should not be defined. It’s not mandatory to define all values in order to enable filtering.
To include services by tags into discovery use folowing configuration:
com.instana.plugin.azure.sqlelasticpool: include_tags: # Comma separated list of tags in key:value format (e.g. env:prod,env:staging)
To exclude services by tags from discovery use folowing configuration:
com.instana.plugin.azure.sqlelasticpool: exclude_tags: # Comma separated list of tags in key:value format (e.g. env:dev,env:test)
To include services by resource groups into discovery use folowing configuration:
com.instana.plugin.azure.sqlelasticpool: include_resource_groups: # Comma separated list of resource groups (e.g. rg_prod,rg_staging)
To exclude services by resource groups from discovery use folowing configuration:
com.instana.plugin.azure.sqlelasticpool: exclude_resource_groups: # Comma separated list of resource groups (e.g. rg_dev,rg_test)
Discovery filtering can be configured on the global level for all Azure services. In case of defining filters for Azure SQL Elastic Pool service, global filters will be overridden. For more details about global Azure service discovery filtering visit Azure Configuration.
Metrics are pulled every minute, which is the resolution Azure provides for monitoring of these services.
|Name||Elastic pool name|
|Resource Group||The resource group of the elastic pool|
|Location||Elastic pool location|
|Subscription Id||The subscription ID of the elastic pool|
|Maximum Size||The storage limit for the elastic pool in bytes|
|State||The state of the elastic pool (Creating, Disabled, Ready)|
|Zone Redundant||Whether or not the elastic pool is zone redundant, which means the replicas of the elastic pool will be spread across multiple availability zones|
|SKU||Pricing tier (SKU)|
|Max Size||The max size of the database expressed in bytes|
|Status||The status of the database|
|SKU||Pricing Tier (SKU)|
|eDTU Limit||Count||Average||Total eDTU utilization of the elastic pool|
|eDTU Used||Count||Average||eDTU utilization of the elastic pool|
|eDTU Percentage||Percent||Average||eDTU utilization percentage|
|CPU Percentage||Percent||Average||CPU resources consumed by all database sessions|
|Storage Limit||Bytes||Average||Total storage size|
|Storage Used||Bytes||Average||Used storage size|
|Storage Percentage||Percent||Average||Used storage percentage|
|Data IO||Percent||Average||Data I/O utilization|
|Log IO||Percent||Average||Log I/O utilization|
|Workers||Percent||Average||Concurrent workers (requests) of the elastic pool service tier limit by the Microsoft Azure SQL Elastic Pool|
|Sessions||Percent||Average||Concurrent sessions of the elastic pool service tier limit|
|In-memory OLTP Storage||Percent||Average||In-memory OLTP Storage (XTP Storage)|
|vCore Limit||Percent||Average||Total number of available vCores|
|vCore Used||Percent||Average||Used vCores|
* eDTU metrics are available only for DTU-based resources
** vCore metrics are available only for vCore-based resources
For each sensor, there is a curated knowledgebase of health signatures that are evaluated continuously against the incoming metrics and are used to raise issues or incidents depending on user impact.
Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of any given entity.
For information about built-events for Azure SQL Elastic Pool sensor, see the Built-in events reference.