What factors are contributing to the increased error rate in Reltio's Identity Resolution service during peak usage hours?

Introduction

Reltio's Identity Resolution service is experiencing an increased error rate during peak usage hours, indicating a critical issue that requires immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term fixes and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking this could be a capacity issue. Can you provide more details on when these peak usage hours typically occur and how long they last?

Why it matters: Understanding the pattern of peak usage helps identify potential capacity constraints. Expected answer: Peak hours occur during business hours, lasting 4-6 hours daily. Impact on approach: If confirmed, we'd focus on scaling solutions during specific time windows.

• Considering the nature of identity resolution, I'm curious about data quality. Have there been any recent changes in data sources or integration processes?

Why it matters: Data quality directly impacts the accuracy of identity resolution. Expected answer: No significant changes in data sources, but a new integration was implemented last month. Impact on approach: If true, we'd investigate the new integration's impact on data processing.

• Given the specificity of "increased error rate," I'm wondering about the exact metrics. What's the normal error rate, and what increase are we seeing?

Why it matters: Quantifying the issue helps prioritize the response and measure improvement. Expected answer: Normal rate is 0.5%, now seeing 2-3% during peak hours. Impact on approach: This would help set clear benchmarks for our solution's success.

• Thinking about system architecture, I'm curious if there have been any recent infrastructure changes or updates to the service?

Why it matters: Infrastructure changes can often lead to unexpected performance issues. Expected answer: A recent cloud migration was completed two weeks ago. Impact on approach: If confirmed, we'd focus on post-migration optimization and configuration issues.