Monitoring Azure Redis Cache
The Azure Redis Cache sensor is automatically deployed and installed after you install the Instana agent.
Note: Learn about the other supported Azure services with our Azure documentation.
Azure Redis Cache sensor can be disabled and it can be filtered by tags and resource groups. It is possible to configure Azure Redis Cache sensor via agent configuration in
com.instana.plugin.azure.rediscache: # 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 Redis Cache sensor can be disabled. To disable monitoring of the Azure Redis Cache services use the following configuration:
com.instana.plugin.azure.rediscache: 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 following configuration:
com.instana.plugin.azure.rediscache: 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 following configuration:
com.instana.plugin.azure.rediscache: 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 following configuration:
com.instana.plugin.azure.rediscache: include_resource_groups: # Comma separated list of resource groups (e.g. rg_prod,rg_staging)
To exclude services by resource groups from discovery use following configuration:
com.instana.plugin.azure.rediscache: 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 Redis Cache service, global filters will be overridden. For more details about global Azure service discovery filtering visit Azure Configuration.
To view the metrics, select Infrastructure in the sidebar of the Instana User interface, click a specific monitored host, and then you can see a host dashboard with all the collected metrics and monitored processes.
Metrics for Redis are pulled every minute, which is the resolution Azure provides for monitoring of these services.
|Name||The name of the Redis instance|
|Resource Group||The resource group of the Redis instance|
|Location||The region where the Redis instance is located|
|Subscription Id||The subscription ID of the Redis instance|
|Version||The Redis version running|
|Host Name||The FQDN the Redis instance is reachable at|
|Provisioning Status||Redis instance provisioning status|
|SSL Port||Redis SSL Port|
|Non SSL Port Enabled||Specifies whether the non-SSL Redis server port is enabled|
|Port||The non-SSL port Redis is listening on|
|SKU||The SKU (Pricing tier) of the Redis cache|
|Clustering Enabled||Specifies whether clustering is enabled|
|Shard Count||The number of shards to be created on a Premium Cluster Cache|
|Max Clients||Maximum number of client connections|
|Max Memory Reserved||The amount of memory, in MB, that is reserved for non-cache operations, such as replication during failover (only available for Standard and Premium caches)|
|Max Fragmentation Memory Reserved||The amount of memory in MB that is reserved to accommodate for memory fragmentation (only available for Standard and Premium caches)|
|Max Memory Delta||The max-memory delta for this Redis instance|
|Static IP||Static IP address. Required when deploying a Redis cache inside an existing Azure Virtual Network|
|Subnet ID||The full resource ID of a subnet in a virtual network to deploy the Redis cache in|
|Redis Metric||Description||Per Shard|
|Connected Clients||Maximum number of client connections||Yes|
|Total Operations||Total number of commands processed by the cache server||Yes|
|Operations per Second||Maximum number of operations per second by the cache server||Yes|
|Cache Hits||Total number of successful key lookups||Yes|
|Cache Misses||Total number of failed key lookups||Yes|
|Gets||Total number of get operations from the cache||Yes|
|Sets||Total number of set operations to the cache||Yes|
|Total keys||Maximum number of keys in the cache||Yes|
|Expired Keys||Total number of items expired from the cache|
|Evicted Keys||Total number of items evicted from the cache due to the maxmemory limit||Yes|
|Used||Maximum amount of cache memory used for key/value pairs in the cache in MB||Yes|
|Used RSS||Maximum amount of cache memory used in MB including fragmentation and metadata||Yes|
|Used Percentage||Maximum percentage of total memory that is being used||No|
|Cache Read||Maximum amount of data read from the cache in Megabytes per second (MB/s)||Yes|
|Cache Write||Maximum amount of data written to the cache in Megabytes per second (MB/s)||Yes|
|Server Load||Maximum percentage of cycles in which the Redis server is busy processing and not waiting idle for messages||Yes|
|CPU||Maximum CPU utilization of the Azure Redis Cache server as a percentage||Yes|
|Cache Latency||The average latency of the cache calculated based off the internode latency of the cache. This metric is measured in microseconds||No|
|Errors||Total number of specific failures and performance issues that the cache could be experiencing||No|
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 Redis Cache sensor, see the Built-in events reference.