Ops AI

Ops AI detects production issues from APM traces, RUM, and logs — and goes a step further by fixing them automatically. With a single click, it analyzes the problem, identifies the affected code using GitHub’s MCP server, and creates a pull request with the suggested fix.

What Ops AI Does

  1. Detects Production Issues Automatically

    Ops AI continuously monitors your application using:

    • APM traces

    • Real User Monitoring (RUM)

    • Application logs

      It intelligently surfaces production issues across backend and frontend — without any manual intervention.

  2. Root Causes Analysis & Fix Generation

    Once an issue is detected, Ops AI uses:

    • Stack traces
    • Error metadata
    • Logs
    • Historical context
    • Your GitHub-linked code files

    to pinpoint the exact line of code responsible and determine the root cause and generate solutions to the issue using these contexts.

  3. PR Creation with Code Fix

    Ops AI generates a fix for the issue. If it’s a coding error, it:

    • Creates a code-level solution and gives a side by side code difference view
    • Opens a PR (Pull Request) in your GitHub repository with the suggested changes
    • Includes context for quick code review and deployment

    Read more about Ops AI use cases here.

Getting Started with Ops AI

1. Install APM & RUM Agents

  • Add the APM agent to your backend services.
    • If you have already installed an APM agent , use our latest SDK to use Ops AI at full capacity.
    • Python SDK Setup
    • Go SDK Setup
    • Node.js SDK Setup
  • For frontend monitoring, include our JavaScript snippet to enable Real User Monitoring(RUM) and fetch issues from your front-end.
  • If your python application is running inside the Kubernetes cluster, you can use Kubernetes auto instrumentation.

2. Connect Your GitHub Repository (Recommended)

GitHub Integration

- Link your GitHub repository to give Ops AI minimal but essential access. - We do not read your entire codebase — only the specific files relevant to an error (via GitHub’s MCP server), and nothing is stored on our end.

Source Code Integration

To enhance accuracy and enable PR creation on the correct branch, include the following build-time environment variables in your CI/CD pipeline or .env file:

- MW_VCS_REPOSITORY_URL: Tells Ops AI which repo the error originated from. - MW_VCS_COMMIT_SHA: Helps Ops AI generate a PR targeting the exact commit branch where the issue occurred.

🛠️ Use your CI/CD system (e.g., GitHub Actions, GitLab CI, Jenkins) or env config to inject these values at build time.

📺 Refer to this video guide to walk through the installation and setup process:

Your Code and Data Stay Private

  • Ops AI only reads the files where an error occurs
  • All access is done via GitHub MCP for maximum security
  • No source code or error context is stored in our systems