Azure Cache for Redis
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:
- Connection logs. These logs contains information about the connections to the cache for security and diagnostic purposes. To learn more about the limitations of connection logging and schemas collected for Azure Cache for Redis, refer to the Azure documentation.
- Cache Metrics. These metrics are available in Microsoft.Cache/redis and Microsoft.Cache/redisEnterprise namespace. For more information on supported metrics, refer to the Azure documentation.
Setupβ
Azure service sends monitoring data to Azure Monitor, which can then stream data to Eventhub. Sumo Logic supports:
- Logs collection from Azure Monitor using our Azure Event Hubs source.
- Metrics collection using our HTTP Logs and Metrics source via Azure Functions deployed using the ARM template.
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
, Azure/RedisCache/Metrics
.
Configure metrics collectionβ
In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, on to an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
- Configure an HTTP Source.
- Configure and deploy the ARM Template.
- Export metrics to Event Hub. Perform below steps for each Azure Cache for Redis that you want to monitor.
- Choose
Stream to an event hub
as destination. - Select
AllMetrics
. - Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by ARM template. You can use the default policy
RootManageSharedAccessKey
as the policy name.
- Choose
Configure logs collectionβ
In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.
- To set up the Azure Event Hubs cloud-to-cloud source in Sumo Logic portal, refer to our Azure Event Hubs source documentation.
- To create the Diagnostic settings in Azure portal, refer to the Azure documentation. Perform below steps for each Azure Cache for Redis that you want to monitor.
- Choose
Stream to an event hub
as the destination. - Select
ConnectedClientList
for Basic, Standard, and Premium tiers andConnection events
for Enterprise and Enterprise Flash tiers. - Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy
RootManageSharedAccessKey
as the policy name.
- Choose
Troubleshootingβ
Azure Event Hubs Sourceβ
Common error types are described here.
You can try restarting the source for ThirdPartyConfig
errors.
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.