Integrations
Integrations connect AccelOS to your observability stack, allowing the AI agent to query metrics, logs, traces, and alerts during incident investigations. AccelOS uses the Model Context Protocol (MCP) to communicate with integrations. This provides a standardized way for the AI agent to interact with different tools while maintaining security and access control.Available Integrations
| Integration | Category | Description |
|---|---|---|
| Datadog | Monitoring | Metrics, APM, logs, incidents |
| Grafana | Monitoring | Dashboards, metrics, alerts |
| Sentry | Error Tracking | Errors, exceptions, performance |
| GitHub | Source Control | Code, PRs, deployments, Actions |
| GitLab | Source Control | Code, MRs, pipelines |
| Confluence | Documentation | Wiki pages, spaces |
| Notion | Documentation | Pages, databases |
| Honeycomb | Observability | Traces, events, queries |
| Elasticsearch | Logs | Log search, aggregations |
| ClickHouse | Analytics | SQL analytics queries |
| Custom MCP | Custom | Your own MCP servers |
General Setup Process
All integrations follow a similar setup process:1
Navigate to Integrations
From the AccelOS sidebar, click Integrations.
2
Select Integration Type
Click on the integration you want to add from the available list.
3
Provide a Name
Give your integration a descriptive name (e.g., “Production Datadog”, “Staging Grafana”).
4
Enter Credentials
Provide the required credentials. These typically include:
- API Key or Token
- Base URL (for self-hosted instances)
- Additional configuration options
5
Test Connection
Click Test Connection to verify the integration is configured correctly.
6
Save
Click Save to activate the integration.
Security & Credentials
Credential Storage
- Credentials are stored in AWS Secrets Manager, isolated per tenant
- Access is scoped to your organization only
- Credentials are never logged or included in error messages
Best Practices
Use Service Accounts
Use Service Accounts
Create dedicated service accounts or API keys for AccelOS rather than using personal credentials. This makes it easier to:
- Audit access
- Rotate credentials
- Limit permissions
Principle of Least Privilege
Principle of Least Privilege
Grant only the permissions AccelOS needs:
- Read-only access is sufficient for most integrations
- Avoid granting write or admin permissions unless necessary
Regular Rotation
Regular Rotation
Rotate API keys periodically:
- Set calendar reminders for key rotation
- Update credentials in AccelOS immediately after rotation
- Test the connection after updating
Multiple Instances
You can connect multiple instances of the same integration type. Common use cases:- Production vs Staging - Separate Datadog accounts for different environments
- Regional Instances - Different Grafana instances per region
- Team-Specific - Dedicated monitoring for different teams
Troubleshooting
Connection Failed
Invalid API Key
Invalid API Key
- Verify the API key is correct and hasn’t been rotated
- Check that the key has the required permissions
- Ensure the key hasn’t expired
Network/Firewall Issues
Network/Firewall Issues
- Verify AccelOS can reach your integration’s API endpoint
- Check if your firewall allows inbound connections from AccelOS IPs
- For self-hosted tools, ensure the URL is accessible
Permission Denied
Permission Denied
- Verify the API key has read permissions
- Check organization-level access controls
- Some integrations require specific scopes or roles
Integration Not Appearing in Investigations
- Ensure the integration status shows as Connected
- Verify the integration is enabled (not disabled)
- Check that your user has permission to access the integration