OpsAI Settings

OpsAI Settings is the single control panel that decides how OpsAI monitors, investigates, and auto-fixes issues across your environment. From here you choose what OpsAI watches (Kubernetes clusters, APM services, and RUM apps), turn Auto-Investigate on or off per source, decide how you get notified, and centralize alerts from Middleware and third-party tools.

When Auto-Investigation is enabled for a source, OpsAI continuously scans its signals (metrics, logs, and traces), correlates them across related entities and recent changes, runs root cause analysis to explain what happened, and proposes a clear fix that you can review and apply.

Prerequisites#

  • For Kubernetes, the Kube agent is installed with opsai.enabled=true and the cluster is visible in Middleware.
  • For APM, the service is instrumented and reporting traces to Middleware.
  • For RUM, the app has the RUM snippet installed and is sending data to Middleware.

Connect your GitHub or Bitbucket repository so OpsAI can read the files related to an error through the MCP server. With the repository linked, OpsAI delivers far more accurate, code-level fixes for APM and RUM issues.

Open OpsAI Settings#

Go to Settings → OpsAI Settings. This page is divided into Auto Investigation, Notification Medium, Notification Frequency, and Alert with OpsAI.

OpsAI Settings Page

Auto Investigation#

The Auto Investigation section lists every source OpsAI can monitor. For each source you set the Monitoring Scope (which entities to watch) and toggle Auto-Investigate on or off:

  • Kubernetes: Set the Monitoring Scope to All Clusters, or select the Specific Clusters you want OpsAI to watch, then flip the Auto-Investigate toggle.
  • Application Performance Monitoring (APM): Choose All Services as the Monitoring Scope, or narrow it down to the Specific Services that matter, and turn on the Auto-Investigate toggle.
  • Real User Monitoring (RUM): Keep the Monitoring Scope at All Apps, or pick the Specific Apps you care about, and enable the Auto-Investigate toggle.
Auto Investigation section with Kubernetes, APM, and RUM sources and the Auto-Investigate toggle

When Auto-Investigate is enabled for a source, OpsAI automatically investigates issues within the scope you defined for that source and proposes a fix. You stay in control and decide whether to apply it.

Set the scope per source#

Each source has its own scope, so you can keep OpsAI focused on the workloads that matter:

  • Kubernetes: Keep All Clusters, or click Select Cluster to pick one or more specific clusters. Only clusters where the agent is installed with opsai.enabled=true appear in this list.
  • APM: Keep All Services, or click Select Services to choose the specific backend services OpsAI should auto-investigate.
  • RUM: Keep All Apps, or click Select App to choose the specific RUM applications OpsAI should auto-investigate.

Enable all automation in one click: From the main OpsAI dashboard you can toggle a single button that turns on Auto-Investigation across all sources at once. The per-source controls on this Settings page let you fine-tune the scope and turn individual sources on or off after that.

Single button on the OpsAI dashboard to enable automation across all sources

Notification Medium#

Notification settings are common across all sources. Choose how you want to be notified when OpsAI detects or fixes an issue automatically. You can configure one or more mediums:

  • Gmail
  • Slack
  • Microsoft Teams
  • Webhook

For each medium, you assign recipients per source (Kubernetes, APM, and RUM), so the right people are notified for each kind of issue. A configured badge shows how many mediums are currently set up.

Notification Medium with Gmail, Slack, Teams, and Webhook options and per-source recipients

Notification Frequency#

Set how often you want to be notified. With Immediate (Real-time), you are alerted as soon as OpsAI detects or fixes an issue. If you select a time frame instead (for example, every 15 minutes), OpsAI summarizes all issues within that window and sends a single, consolidated notification.

Confirm changes#

After you change the scope, toggle a source, or update notifications, a toast confirms the update and states "Your changes have been saved. Updates will appear within 5 minutes."

Confirm Changes - Your changes have been saved

Import Alerts into OpsAI#

OpsAI allows you to ingest and centralize alerts from Middleware, Grafana, and Datadog. Alerts can appear in the OpsAI listing in two ways: enable native Middleware alert ingestion or connect third-party integrations.

Native Middleware alerts

Go to Settings > OpsAI Settings and enable the Alert with OpsAI toggle.

Alert Ingestions toggle in OpsAI Settings

Import alerts from third-party integrations

To include alerts from Grafana or Datadog in the OpsAI listing:

  • Connect Grafana and set up the webhook (Contact Point + Notification policies) to send alerts to Middleware, then run OpsAI investigations on those alerts using your Grafana integration and capabilities.

  • Connect Datadog to ingest alerts and run OpsAI investigations on Monitor and Kubernetes alerts with metrics, logs, and traces.

Tips and troubleshooting#

  • Cluster not listed: Verify the agent is installed with opsai.enabled=true and the cluster name matches what you expect.

  • Service or app not listed: Confirm the APM service or RUM app is instrumented and actively reporting data to Middleware.

  • Nothing shows in OpsAI: Check that Auto-Investigate is enabled for the source and that at least one entity is included in its Monitoring Scope.

Need assistance or want to learn more about Middleware? Contact our support team at [email protected] or join our Slack channel.