Assistance Required for Redis Error Metrics and Logging

Nitin Parmar-Tss consultancy 71 Reputation points
2024-06-29T08:50:15.62+00:00

Hi Team.

We are currently utilizing the Azure Redis cache service in our production environment, and we have encountered an issue with monitoring error metrics. Specifically, we can see an increasing error count metric but are unable to identify the exact cause of these errors due to the lack of detailed logs.

Without these logs, it is challenging to diagnose and address the underlying issues effectively. We are seeking guidance on the following points:

User's image

Azure Cache for Redis
Azure Cache for Redis
An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.
227 questions
Azure ISV (Independent Software Vendors) and Startups
Azure ISV (Independent Software Vendors) and Startups
Azure: A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.ISV (Independent Software Vendors) and Startups: A Microsoft program that helps customers adopt Microsoft Cloud solutions and drive user adoption.
91 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amrinder Singh 3,875 Reputation points Microsoft Employee
    2024-07-01T05:14:03.27+00:00

    Hi Nitin Parmar-Tss consultancy - Thanks for reaching out.

    I would suggest you leverage "Apply Splitting" option. That shall help in identifying the type of errors happening on your Redis cache. Below is the explanation for different type of Errors:

    https://video2.skills-academy.com/en-us/azure/azure-cache-for-redis/monitor-cache-reference

    User's image

    Once identified, it shall help in taking the next action and to analyze further. e.g..

    If it is failover, it could be possibly due to patching but if it occurring very frequently something might be wrong at the backend.

    If it AOF/RDB/Import/Export, it could some issue with configuration or some backend issue.

    For Unresponsive client, there is possibly some congestion on the clients.

    Hope that helps!

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments
  2. ShaktiSingh-MSFT 14,201 Reputation points Microsoft Employee
    2024-07-01T05:16:09.3133333+00:00

    Hi Nitin Parmar-Tss consultancy,

    Welcome to Microsoft Q&A forum.

    As I understand, you need assistance for Redis Error Metrics and Logging.

    As per the screenshot, it appears that the metrics is for Errors: The number errors that occurred on the cache.

    Specific failures and performance issues that the cache could be experiencing during a specified reporting interval. This metric has eight dimensions representing different error types. The error types represented now are as follows:

    • Failover – when a cache fails over (subordinate promotes to primary)
    • Dataloss – when there's data loss on the cache
    • UnresponsiveClients – when the clients aren't reading data from the server fast enough, and specifically, when the number of bytes in the Redis server output buffer for a client goes over 1,000,000 bytes
    • AOF – when there's an issue related to AOF persistence
    • RDB – when there's an issue related to RDB persistence
    • Import – when there's an issue related to Import RDB
    • Export – when there's an issue related to Export RDB
    • AADAuthenticationFailure - deprecated
    • AADTokenExpired - deprecated
    • MicrosoftEntraAuthenticationFailure - when there's an authentication failure using Microsoft Entra access token
    • MicrosoftEntraTokenExpired - when a Microsoft Entra access token used for authentication isn't renewed and it expires

    Reference: https://video2.skills-academy.com/en-us/azure/azure-cache-for-redis/monitor-cache-reference

    Please provide more information regarding the configuration of your Azure cache for redis so that we can replicate similar cache at our end and check.

    Thanks.

    0 comments