Skip to main content

Azure Cache for Redis

Thumbnail icon

Azure Cache for Redis provides an in-memory data store based on the Redis software. It offers both the Redis open-source (OSS Redis) and a commercial product from Redis Inc. (Redis Enterprise) as a managed service. This integration helps in tracking cache performance (miss rate, latency, read and write rate) and monitor resource usage (CPU, used memory, server load, and connections) of your instances.

Log and metric types

For Azure Cache for Redis, you can collect the following logs and metrics:

Setup

Azure service sends monitoring data to Azure Monitor, which can then stream data to Eventhub. Sumo Logic supports:

You must explicitly enable diagnostic settings for each Azure Cache for Redis you want to monitor. You can forward logs to the same event hub provided they satisfy the limitations and permissions as described here.

When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: Azure/RedisCache/Logs and Azure/RedisCache/Metrics.

Configure metrics collection

To set up the Azure Metrics source in Sumo Logic, refer to Azure Metrics Source.

Configure logs collection

Diagnostic logs

In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.

  1. To set up the Azure Event Hubs source in Sumo Logic, refer to the Azure Event Hubs Source for Logs.
  2. To create the diagnostic settings in Azure portal, refer to the Azure documentation. Perform the steps below for each azure redis cache account that you want to monitor.
    1. Choose Stream to an event hub as the destination.
    2. Select allLogs.
    3. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy RootManageSharedAccessKey as the policy name.
    Azure Redis Cache logs
  3. Tag the location field in the source with right location value.
    Azure Redis Cache Tag Location

Activity Logs

To collect activity logs, follow the instructions here. Do not perform this step if you are already collecting activity logs for a subscription.

note

Since this source contains logs from multiple regions, ensure that you do not tag this source with the location tag.

Installing the Azure Redis Cache app

Now that you have set up data collection, install the Azure Load Balancer Sumo Logic app to use the pre-configured dashboards that provide visibility into your environment for real-time analysis of overall usage.

To install the app, do the following:

note

Next-Gen App: To install or update the app, you must be an account administrator or a user with Manage Apps, Manage Monitors, Manage Fields, Manage Metric Rules, and Manage Collectors capabilities depending upon the different content types part of the app.

  1. Select App Catalog.
  2. In the 🔎 Search Apps field, run a search for your desired app, then select it.
  3. Click Install App.
    note

    Sometimes this button says Add Integration.

  4. Click Next in the Setup Data section.
  5. In the Configure App section of your respective app, complete the following field.
    1. Index. Specify value for _index if the collection is configured with custom partition. Learn more. Default value is set to sumologic_default (default partition)
  6. Click Next. You will be redirected to the Preview & Done section.

Post-installation

Once your app is installed, it will appear in your Installed Apps folder, and dashboard panels will start to fill automatically.

Each panel slowly fills with data matching the time range query received since the panel was created. Results will not immediately be available but will be updated with full graphs and charts over time.

As part of the app installation process, the following fields will be created by default:

  • tenant_name. This field is tagged at the collector level. You can get the tenant name using the instructions here.
  • location. The region to which the resource name belongs to.
  • subscription_id. ID associated with a subscription where the resource is present.
  • resource_group. The resource group name where the Azure resource is present.
  • provider_name. Azure resource provider name (for example, Microsoft.Network).
  • resource_type. Azure resource type (for example, storage accounts).
  • resource_name. The name of the resource (for example, storage account name).
  • service_type. Type of the service that can be accessed with an Azure resource.
  • service_name. Services that can be accessed with an Azure resource (for example, in Azure Container Instances the service is Subscriptions).

Viewing the Azure Cache for Redis dashboards

All dashboards have a set of filters that you can apply to the entire dashboard. Use these filters to drill down and examine the data to a granular level.

  • You can change the time range for a dashboard or panel by selecting a predefined interval from a drop-down list, choosing a recently used time range, or specifying custom dates and times. Learn more.
  • You can use template variables to drill down and examine the data on a granular level. For more information, see Filtering Dashboards with Template Variables.
  • Many of the Next-Gen apps allow you to provide the Index at the installation time and a default value for this key (sumologic_default). Based on your input, the app dashboards will be parameterized with a dashboard variable, allowing you to change the data partition queried by all panels. This restricts the query scope of all the dashboard queries to a specific data partition.

Administrative Operations

The Azure Cache for Redis - Administrative Operations dashboard provides details like distribution by operation type, by operation, recent delete operations, top 10 operations that caused most errors, and users/applications by operation type.

Azure Cache for Redis - Administrative Operations

Connections(Enterprise)

The Azure Cache for Redis - Connections(Enterprise) provides details like connections by location, total unique connected clients, total connections, event types, disconnection events, failure by operations, connected clients, cache read vs write, and hit vs misses.

Azure Cache for Redis - Connections(Enterprise

Connections(Non-Enterprise)

The Azure Cache for Redis - Connections(Non-Enterprise) dashboard provides details like connections by location, total unique connected clients, total connections, top 10 ip's by connection count, connections by resource name, connected clients (instance based), connected clients, cache read vs write, and hit vs misses.

Azure Cache for Redis - Connections(Non-Enterprise)

Geo Replication

The Azure Cache for Redis - Geo Replication dashboard provides details like geo-replication healthy - fetched from geo-secondary cache, geo-replication full sync events - fetched from geo-secondary cache, geo-replication data sync offset - fetched from geo-primary cache, and geo-replication connectivity lag - fetched from geo-secondary cache.

Azure Cache for Redis - Geo Replication

MSEntra Authentication Audit

The Azure Cache for Redis - MSEntra Authentication Audit dashboard provides details like requests by location, requests by resource name, requests by username, and MSEntra authentication audit details.

Azure Cache for Redis - MSEntra Authentication Audit

Policy and Recommendations

The Azure Cache for Redis - Policy and Recommendations dashboard provides details like total success policy events, total failed policy events, total recommendation events, and recent recommendation events.

Azure Cache for Redis - Policy and Recommendations

Resource Operations (Enterprise)

The Azure Cache for Redis - Resource Operations(Enterprise) dashboard provides details like total operations, ops per second (max), gets, sets, evicted key count, and expired key count.

Azure Cache for Redis - Resource Operations(Enterprise)

Resource Operations (Non-Enterprise)

The Azure Cache for Redis - Resource Operations(Non-Enterprise) dashboard provides details like total operations, ops per second (max), gets, sets, evicted key count, and expired key count.

Azure Cache for Redis - Resource Operations(Non-Enterprise)

Resource Overview (Enterprise)

The Azure Cache for Redis - Resource Overview(Enterprise) dashboard provides details like max server load %, max CPU %, max bytes used, max number of connected clients, and errors.

Azure Cache for Redis - Resource Overview(Enterprise)

Resource Overview (Non-Enterprise)

The Azure Cache for Redis - Resource Overview(Non-Enterprise) dashboard provides details like max server load %, max CPU %, max bytes used, max number of connected clients, and errors.

Azure Cache for Redis - Resource Overview(Non-Enterprise)

Resource Performance (Enterprise)

The Azure Cache for Redis - Resource Performance(Enterprise) dashboard provides details like cache hits, cache misses, cache write (max), cache read (max), cache latency microseconds, and 99th percentile latency (max).

Azure Cache for Redis - Resource Performance(Enterprise)

Resource Performance (Non-Enterprise)

The Azure Cache for Redis - Resource Performance(Non-Enterprise) dashboard provides details like cache hits, cache misses, cache write (max), cache read (max), cache latency microseconds, and 99th percentile latency (max).

Azure Cache for Redis - Resource Performance(Non-Enterprise)

Azure Cache for Redis alerts

These alerts are metric based and will work for all Azure Cache for Redis.

Alert NameAlert Description and ConditionsAlert ConditionRecover Condition
Azure Cache For Redis - Cache ReadThis alert is triggered when Average Cache Read bytes are greater than 140625000. Also, a warning type alert will be triggered when Cache Read Units bytes are greater than 130625000.bytes >= 140625000bytes < 140625000
Azure Cache For Redis - Connected ClientsThis alert is triggered when Connected Clients count is greater than 5625. Also, a warning type alert will be triggered when Connected Clients count is greater than 4625.count >= 5625count < 5625
Azure Cache For Redis - CPU UtilizationThis alert is triggered when CPU Utilization percentage greater than 80. Also a warning type alert will be triggered when CPU Utilization percentage greater than 70.percentage >= 80percentage < 80
Azure Cache For Redis - Server LoadThis alert is triggered when Server Load percentage greater than 80. Also a warning type alert will be triggered when Server Load percentage greater than 70.percentage >= 80percentage < 80
Azure Cache For Redis - Used Memory PercentageThis alert is triggered when Used Memory percentage greater than 80. Also a warning type alert will be triggered when Used Memory percentage greater than 70.percentage >= 80percentage < 80

Troubleshooting

HTTP Logs and Metrics Source used by Azure Functions

To troubleshoot metrics collection, follow the instructions in Collect Metrics from Azure Monitor > Troubleshooting metrics collection.

Status
Legal
Privacy Statement
Terms of Use

Copyright © 2025 by Sumo Logic, Inc.