Getting Started FAQ
How long does setup take?
About 10 minutes for a basic setup: create an account, add a cluster, install the Kubernetes Agent via Helm, and connect an alerting source. See the Quick Start guide.
What Kubernetes versions are supported?
Kubernetes 1.24 and later. This includes EKS, GKE, AKS, and self-hosted distributions. See Version Compatibility.
What monitoring systems work with OpsWorker?
Prometheus AlertManager, Grafana Alerting (9+), Datadog, and Amazon CloudWatch. OpsWorker receives alerts via webhook — no changes to your monitoring setup beyond adding a webhook receiver.
Do I need to change my existing monitoring setup?
No. OpsWorker adds a webhook receiver to your existing monitoring system. Your current alerts, dashboards, and notification channels continue to work unchanged.
How many clusters can I connect?
This depends on your plan. Contact the OpsWorker team for plan details.
Can I try OpsWorker before committing?
Yes. Contact the OpsWorker team for a free trial. You can connect your clusters and run investigations during the trial period.
What happens during the first investigation?
OpsWorker receives the alert, discovers affected Kubernetes resources, gathers logs/events/configs, analyzes the data with AI, and delivers a root cause analysis with fix recommendations to Slack. The entire process takes under 2 minutes.
How do I verify everything is working?
Use the Test Integration button in your cluster settings. It sends a synthetic alert through the full pipeline and verifies that the agent, investigation engine, and Slack notification are all working.
Can I use OpsWorker with multiple teams?
Yes. Create separate workspaces for each team. Each workspace has its own clusters, alert rules, and notification channels. Users are assigned to specific workspaces.
What if I don't use Kubernetes?
OpsWorker is specifically designed for Kubernetes environments. It requires a Kubernetes cluster with the OpsWorker Agent installed.