Customer Onboarding Guide

This guide walks through the complete onboarding journey from account signup to your first automated incident response.

Time to complete: ~30 minutes

Step 1: Sign Up and Choose a Plan

1. Visit atlasai.com  and click Get Started Free
2. Enter your work email and company name
3. Choose a plan:

4. Complete payment (Razorpay) — your tenant is provisioned instantly.

Step 2: Access Your Tenant Plane

After payment confirmation, you receive:

• Login URL: https://app.atlasai.com (Shared TP) or https://<your-subdomain>.atlasai.com (Dedicated)
• Admin email: the email used during signup
• Temporary password: sent via email (change on first login)

Login:

1. Go to your TP URL → /login
2. Enter your credentials
3. Set a new password when prompted

Enterprise SSO: If your organization uses Okta, Azure AD, or Google Workspace, configure SAML/OIDC in Settings → SSO before inviting users.

Step 3: Configure Your First Data Source

Navigate to Settings → Data Sources → Add Connector:

Option A: Prometheus (metrics)

# prometheus.yml — add AtlasAI remote_write
remote_write:
  - url: https://<your-tp>/api/ingest/prometheus
    bearer_token: <your-collector-token>
    queue_config:
      max_samples_per_send: 10000

Option B: AtlasAI Edge Agent (full observability)

Install the collector on your infrastructure:

curl -sSL https://get.atlasai.com/agent | \
  TP_URL=https://<your-tp> \
  TENANT_ID=<your-tenant-id> \
  COLLECTOR_TOKEN=<token> \
  bash

The agent collects logs, metrics, traces, and SSH-executes runbooks.

Option C: Cloud Connector (AWS/Azure/GCP)

1. Settings → Connectors → AWS → Paste your IAM Role ARN
2. AtlasAI assumes the role and discovers EC2, RDS, EKS, Lambda assets

Step 4: Seed Your CMDB

After connectors are active, run CMDB auto-discovery:

Settings → CMDB → Run Discovery

This discovers all infrastructure assets and creates Configuration Items (CIs). You can also manually create CIs:

POST /api/cmdb/items
{ "name": "web-server-01", "class": "server", "environment": "production" }

Best practice: Tag your infrastructure with AtlasAI=true in AWS for automatic discovery.

Step 5: Configure Alert Policies

Navigate to Alerts → Alert Policies → Create Policy:

{
  "name": "High CPU Alert",
  "condition": { "metric": "cpu_usage", "operator": ">", "threshold": 85, "for": "5m" },
  "severity": "P2",
  "notify": ["ops-team@example.com"],
  "auto_create_incident": true
}

Or use the UI builder — no code required.

Step 6: Create Your First Runbook

Runbooks automate remediation steps. Navigate to Runbooks → Create Runbook:

1. Add steps (SSH command, HTTP call, notification, approval gate)
2. Click AI Generate to create steps from a description
3. Publish the runbook to make it available for incidents

Example SSH step:

{
  "type": "command",
  "title": "Restart application server",
  "command": "sudo systemctl restart app && sleep 5 && systemctl is-active app"
}

Step 7: Trigger Your First Incident

You can inject a test incident to validate the full pipeline:

POST /api/demo/inject-incident
{ "severity": "P2", "title": "High CPU on web-server-01", "source": "prometheus" }

Or wait for a real alert — when your alert policy fires, AtlasAI will:

1. Create an incident automatically (INC-00000001)
2. Run RCA to identify the root cause
3. Suggest relevant runbooks
4. Notify your on-call team

Step 8: Invite Your Team

Settings → Users → Invite User

For enterprise RBAC with custom roles: Settings → Roles & Permissions → Create Role

Step 9: Configure On-Call Schedule

Navigate to ITSM → On-Call → Create Schedule:

1. Add team members
2. Set rotation (daily, weekly, custom)
3. Link to alert policies for automatic paging

Step 10: Review Your Dashboard

Go to Command Center to see:

• Real-time incident radar
• Infrastructure health KPIs
• AI insights and anomaly detection
• SLA compliance scores
• Automation success rates

Next Steps

• Set up SAML SSO →
• Configure dedicated TP →
• AI use cases →
• API Reference →
• Support → 

Troubleshooting

No data in dashboards after connecting Prometheus?

• Verify remote_write is enabled in your Prometheus config
• Check connector health at Settings → Data Sources → Health
• Ensure your collector token has not expired

Login not working?

• Verify your tenant ID in the URL (x-tenant-id header must match)
• If using SSO, check your IdP application configuration
• Contact support at support@atlasai.com