Skip to main content
Version: NG-3.1

RCA Incidents

Introduction​

RCA Incidents represent user-impacting situations detected by our vuRCA Bot. When you access this section, you'll receive detailed information about the incident, including its causes. This helps you understand and learn from previous user-impacting events.

You'll receive insights into upcoming problems and potential reasons for these forecasts. This proactive approach enables you to address concerns before they fully impact users, ensuring a smoother experience.

Why is this feature useful​

  • RCA Incidents helps operations teams quickly identify, investigate, and resolve user-impacting issues across business journeys and system components. Instead of manually correlating metrics, logs, and infrastructure events, the platform automatically detects anomalies, identifies probable root causes, and presents actionable insights in a single view.
  • By providing incident statistics, root cause analysis, impacted segments, and recommended actions, RCA Incidents enables teams to reduce detection and resolution times, improve service reliability, and proactively address issues before they significantly affect end users.

When to use this feature​

Use RCA Incidents when you need to:

  • Monitor active incidents affecting business services.
  • Review previously detected and resolved incidents.
  • Analyze probable root causes of system anomalies.
  • Understand impacted user journeys and business segments.
  • Track incident health metrics such as MTTD, MTTR, MTTFRC, and AETC.
  • Validate incident accuracy and provide feedback to improve RCA predictions.
  • Generate incident reports for operational reviews and stakeholder communication.
  • Investigate recurring issues and identify patterns across incidents.

Step-by-step instructions​

Follow these steps to investigate an incident:

  1. Navigate to Observability > RCA Incidents.
  2. Select the required time range.
  3. Apply filters based on incident status or severity.
  4. Review KPI statistics in the Impact on End Users section.
  5. Browse available Incident Cards.
  6. Select an Incident Card to view a detailed analysis.
  7. Review the RCA tab to understand probable root causes and affected components.
  8. Open the Journey Graph to visualize impacted components.
  9. Review Recommended Actions if available.
  10. Switch to the Summary tab to analyze impacted segments and abnormal metrics.
  11. Provide feedback, share reports, or create tickets as required.
  12. Review configuration settings if deeper analysis or tuning is needed.

What happens after the step​

After opening an incident:

  • Detailed incident information becomes available.
  • Root cause candidates are displayed based on RCA analysis.
  • Impacted components and business segments are highlighted.
  • Time-series visualizations display anomalous behavior.
  • Recommended actions help guide investigation and resolution.
  • Incident statistics such as TTD, TTR, and TTFRC become available.
  • Users can provide feedback to improve future incident detection accuracy.
  • Reports can be generated and shared with stakeholders.
  • Incident status can be reviewed and updated when required.
  1. Accessing RCA Incidents is your hub for managing and understanding user-impacting situations within your system. Here, you can:
    • Stay Informed About Ongoing Issues: Keep an eye on real-time incidents, both auto-resolved and user-cleared.
    • Predict Challenges: Anticipate potential issues to take proactive measures and ensure system reliability.
  2. RCA for an Incident: In your journey to ensure system reliability, the Incidents section is your go-to resource. By simply clicking "RCA Incidents" from the left Navigation section, you can effortlessly access a wealth of information. Just scroll down a bit and you will see the following tabs:
    • RCA: Delve into the probable root causes and components responsible for incidents, all explained in plain language.
    • Summary: Gain in-depth insights into each incident, including abnormal components, impacted segments, and metrics.
  3. Additional Features: The Incident Management System goes beyond incident detection and root cause analysis. It empowers you to provide essential feedback, share crucial reports, and configure the system according to your specific needs.
    • User Feedback: Shape incident detection by providing feedback on detected incidents. Mark false alarms and manually close resolved incidents, ensuring more accurate future detections.
    • Reports: Efficiently communicate incident details by downloading or sharing reports via email, Slack, WhatsApp, and more.
    • Settings: Tailor the system to your requirements by reviewing and adjusting various parameters, ensuring it aligns perfectly with your needs.
RCA Incidents help you spot issues, understand what caused them, and take action — all before users even notice something’s wrong

FAQs​

What are RCA Incidents in vuSmartMaps?

RCA Incidents are user-impacting events automatically detected by the vuRCA Bot. Each incident provides detailed insights about the issue, its probable root cause, affected components, and recommendations for resolution.

How does RCA help improve system reliability?

By analyzing past incidents, identifying patterns, and highlighting likely root causes, RCA helps you proactively prevent recurring issues and reduce downtime, improving overall system performance and user experience.

What’s the benefit of using the RCA Incidents section?

You can monitor real-time issues, review past incidents, track detection and resolution times, and take preventive measures—all in one place.