> ## Documentation Index
> Fetch the complete documentation index at: https://docs.resolve.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect an Integration

<Info>
  **Guided Tour · Part 2 of 5**
  [Resolve Overview](/resolve-overview) → Connect an Integration → [Team Knowledge](/D5xH-team-knowledge) → [Auto Investigations](/auto-investigations) → [Tuning Accuracy](/tuning-accuracy)
</Info>

This guide walks you through connecting ResolveAI to your production systems. By the end, you'll be investigating your real infrastructure, logs, metrics, and code.

## Prerequisites

Before you begin, ensure you have:

* A ResolveAI account ([Sign up here](http://app0.resolve.ai))
* Access credentials for your primary tools (Grafana, Datadog, AWS, etc.)
* Permissions to create API tokens or service accounts

## Step 1: Name Your Organization

After logging in and selecting **Set up ResolveAI for your environment**, you'll name your organization.

<Info>
  Colleagues with the same email domain can automatically join this organization once it's created.
</Info>

<p align="center">
  <img src="https://mintcdn.com/resolveai-0e94a547/TSKPziqa8xE8YA7n/images/org-name.png?fit=max&auto=format&n=TSKPziqa8xE8YA7n&q=85&s=ff7cb1977d5d0399c3e7d73eda33e2cc" width="400" alt="Name your organization" data-path="images/org-name.png" />
</p>

## Step 2: Connect integrations

Give Resolve access to your stack. The more data sources you connect, the more powerful Resolve investigations and cross-stack correlations become.

We recommend starting with these types of integrations:

1. Observability: Logs, metrics, dashboards, traces, alerts
2. Code: Git integration
3. Infrastructure: AWS, GCP, Kubernetes
4. Knowledge: Confluence, Notion
5. Chat: Slack, MS Teams

<p align="center">
  <img src="https://mintcdn.com/resolveai-0e94a547/TSKPziqa8xE8YA7n/images/integrations.png?fit=max&auto=format&n=TSKPziqa8xE8YA7n&q=85&s=b88b69da5d04b95d0a3729b045464867" width="400" alt="Connect a first integration" data-path="images/integrations.png" />
</p>

## Step 3: Configure Your Integration

Each integration follows a simple, guided flow. Let's look at Grafana as an example:

1. **Name**: (e.g., `prod-grafana`) — Helps distinguish between multiple instances.
2. **Connection Details**: Enter your instance URL and relevant credentials (API token or OAuth).

<p align="center">
  <img src="https://mintcdn.com/resolveai-0e94a547/TSKPziqa8xE8YA7n/images/datadog-integration-modal.png?fit=max&auto=format&n=TSKPziqa8xE8YA7n&q=85&s=3e7e9f79080d7756c64a6c79be5ea631" width="400" alt="Configure integration" data-path="images/datadog-integration-modal.png" />
</p>

<Info>
  **Need deep technical details?** Check our [Integration Reference](/setup-and-integrations) for step-by-step permissions and troubleshooting for every tool.
</Info>

## Step 4: Start Investigating

Once your integrations show a green checkmark, you're ready. Click **Ask your first question** to enter the main interface with your live data.

### Recommended First Steps

Try these prompts to see ResolveAI in action with your systems:

* `“What integrations are configured?”`
* `“Show me the most important services and their dependencies”`
* `“What were the most recent deployments?”`

## Pro Tips for Success

<Info>
  **Combine for Context:** Connect at least two integrations (e.g., Code + Telemetry) to unlock the strongest insights, such as linking performance spikes directly to recent commits.
</Info>

* **Descriptive Naming:** Clear names help when you're managing multiple clusters or cloud accounts.
* **Incremental Setup:** You don't need everything at once. Start with your primary logging and monitoring tools, then expand.

***

## Troubleshooting & Support

* **Connection Failures:** Double-check API permissions and URL accessibility.
* **Missing Tools:** Scroll through the full list or reach out to us if you need a custom integration.

***

## What's next

With your data flowing in, the next step is teaching Resolve about *your* systems so investigations get faster and more accurate.

**Next:** [Part 3 — Team Knowledge](/D5xH-team-knowledge)
**Previous:** [Part 1 — Resolve Overview](/resolve-overview)