# Rocky AI Error Analysis from Checkly > Rocky AI reads your logs, traces, and check runs to pinpoint why a check failed and who it impacts, so your team resolves incidents faster. Source: https://www.checklyhq.com/product/ai-analysis/ --- ROCKY AI # AI-powered root cause analysis for engineering teams and agents Rocky AI analyzes check failures in seconds, not hours. Get instant error categorization, user impact assessment, and actionable fix suggestions. [Start For Free](https://app.checklyhq.com/signup)[View Documentation](https://www.checklyhq.com/docs/resolve/ai-root-cause-analysis/overview/) ### World-class engineering and SRE teams depend on Checkly to deliver reliable digital experiences ### Instant Diagnosis Rocky AI analyzes failures the moment they happen. Get actionable insights in seconds, not after hours of manual debugging and toil. ### Context-Aware Analysis Rocky AI understands your check code, OpenTelemetry and Playwright traces, screenshots, and logs to provide accurate assessments with full context. ### Automated Error Grouping See similar errors grouped together and understand the root cause of the issue. Seen 1097 times since 6 months ago in 🇺🇸 🇨🇦 🇦🇺 +10 Rocky AI analysis Infrastructure Error ## Rocky AI accelerates debugging, in the heat of an outage From error classification to code fix suggestions, Rocky AI provides comprehensive failure analysis at every step. ### Root Cause Analysis Get to the why, not just the what Rocky AI generates detailed diagnostics with supporting evidence from screenshots, Playwright and OpenTelemetry traces, and logs. Understand the true cause of failures with AI-powered analysis. Detailed Diagnostics Evidence Collection OpenTelemetry Traces Screenshot Context Root Cause The application server for https://shop.example.com/ is returning HTTP 500 Internal Server Error for the homepage request, indicating a backend failure in the product-catalog-service rather than a test code issue. • HTTP 500 Internal Server Error Explanation • Playwright page.goto() Documentation Evidence 3 • The error message shows the assertion expected a status code < 400 but the received status code was 500, confirming a server-side failure. error • The trace logs the network request to https://shop.example.com/ with method GET and status 500, matching the failed assertion and indicating the homepage itself returns 500. playwright trace • The OpenTelemetry trace for the request shows the frontend span returning status 500, with the error originating in a downstream product-catalog-service gRPC span that failed to fetch products — confirming the failure is in the backend service rather than the test code. opentelemetry trace ### User Impact Assessment Understand who is affected Rocky AI identifies which user groups, features, and workflows are impacted by the failure. Prioritize fixes based on real business impact. Affected Users Feature Impact Workflow Disruption Business Priority User impact Users cannot load the homepage; the server responds with an internal error instead of displaying the storefront. This prevents access to any functionality that depends on the homepage loading successfully. Steps 2 ### Error Categorization Classify failures automatically Rocky AI determines whether errors stem from code issues, infrastructure problems, third-party service failures, or timing problems. No more guessing games. Code Errors Infrastructure Issues Third-Party Failures Timing Problems Infrastructure Error Playwright Error Network Error ### Step Summarization Understand what your checks do Rocky AI analyzes your Playwright scripts and API checks to provide human-readable summaries of each step. Know exactly what was tested and where it failed. Script Analysis Step Breakdown Failure Location Action Summary Steps 6 Open the homepage. Click on the "National Park Foundation" product link. Select quantity 2 for the product. Click the "Add To Cart" button. Click the "Place Order" button on the checkout page. Verify that the "Your order is complete!" confirmation heading is visible. Timed out 5000ms waiting for expect(locator).toBeVisible() for heading 'Your order is complete!' ## From failure to fix in seconds When a check fails, Rocky AI immediately analyzes all available artifacts—error messages, screenshots, Playwright traces from the browser, OpenTelemetry traces from your backend, and logs—to deliver comprehensive failure assessments with suggested code fixes. app.checklyhq.com ## Get AI-powered remediation brought to any tool or agent Rocky AI integrates with your existing workflow. Send failure analysis and fix suggestions directly to the tools and agents your team already uses. ## Frequently Asked Questions Everything you need to know about Rocky AI and automated root cause analysis. Rocky AI analyzes error messages, stack traces, console logs, screenshots, video recordings, Playwright traces, OpenTelemetry traces, network requests, and your check code to provide comprehensive failure assessments. Rocky AI is trained on monitoring-specific patterns and understands Playwright, API testing, and common infrastructure issues. While no AI is perfect, Rocky significantly accelerates diagnosis by surfacing relevant context and suggesting likely causes. Rocky AI analyzes your check code at runtime to provide context-aware suggestions. It understands your specific implementation patterns to suggest fixes that match your coding style. No. Your check data, code, and analysis results are not used to train any AI models. Rocky AI processes your data securely and results are only visible within your Checkly account. Rocky AI is available on Team and Enterprise plans. Once enabled in your account settings, it automatically analyzes failed checks and provides insights in the check results view. No additional configuration required. ## Stop debugging. Start fixing . Let Rocky AI handle the analysis while you focus on building. Get AI-powered root cause analysis on every failed check. [Start For Free](https://app.checklyhq.com/signup)[Request Demo](https://www.checklyhq.com/demo-request/)