Connecting Data Sources

StackPilot's power comes from connecting your existing development and operations tools. By integrating with your monitoring, alerting, and version control systems, StackPilot can provide comprehensive, code-aware root cause analysis.

Supported Connections

Version Control

• GitHub - Access commits, pull requests, and code changes for correlation with incidents
• GitLab - Track code deployments and changes that may cause issues
• Bitbucket - Integrate repository data for comprehensive analysis

Monitoring & Observability

• Datadog - Import metrics, logs, and traces for correlation analysis
• New Relic - Access APM data and performance metrics
• Sentry - Automatically import error tracking and exception data
• Grafana - Connect dashboards and alert data
• Prometheus - Import time-series metrics and alerting rules

Incident Management

• PagerDuty - Sync incidents and on-call schedules
• Opsgenie - Import alert data and escalation policies
• VictorOps (Splunk On-Call) - Connect incident workflows

Communication

• Slack - Post updates and enable collaborative incident response
• Microsoft Teams - Integrate with your team communication workflow
• Discord - Connect with development team channels

Deployment & CI/CD

• Jenkins - Track deployment pipelines and build failures
• GitHub Actions - Monitor workflow failures and deployment issues
• GitLab CI - Connect pipeline data with incident correlation
• ArgoCD - Track Kubernetes deployment issues
• Spinnaker - Monitor multi-cloud deployment failures

Connection Setup Process

1. Navigate to Connections

1. Go to your project dashboard
2. Click on the Connections tab in the sidebar
3. Browse available integrations

2. Choose Connection Method

Most integrations offer multiple authentication methods:

• OAuth - Recommended for quick, secure setup
• API Keys - For fine-grained access control
• Webhooks - For real-time event streaming

3. Configure Permissions

When connecting, ensure StackPilot has access to:

• Read access to logs, metrics, and incident data
• Repository access for code correlation (read-only)
• Webhook permissions for real-time updates

4. Test Connection

After setup, StackPilot will:

• Verify connectivity to your tools
• Import recent data for analysis
• Display connection status and health

Best Practices

Essential Connections

For maximum effectiveness, connect these critical tools:

1. Version Control (GitHub/GitLab) - Enable code correlation
2. Error Tracking (Sentry) - Automatic incident detection
3. APM Tool (Datadog/New Relic) - Performance and trace data
4. Communication (Slack) - Collaborative incident response

Permission Management

• Use dedicated service accounts for API access when possible
• Limit permissions to read-only unless write access is specifically needed
• Regularly rotate API keys and tokens for security
• Monitor connection health in the StackPilot dashboard

Data Retention

• Configure retention policies based on your needs
• Understand what data StackPilot stores vs. queries in real-time
• Set up data filtering to focus on relevant services and applications

Connection Troubleshooting

Common Issues

Authentication Failures

• Expired tokens: Re-authenticate using OAuth or update API keys
• Permission denied: Verify the service account has required permissions
• Rate limiting: Check if API rate limits are being exceeded

Missing Data

• Webhook delays: Verify webhook configurations are active
• Filtering issues: Check if data filters are too restrictive
• Service downtime: Verify the connected service is operational

Connection Health

• Monitor connection status in the Settings → Connections page
• Set up alerts for connection failures
• Regularly test integrations after system updates

Getting Help

If you encounter issues:

1. Check the connection status in your dashboard
2. Review integration logs for error details
3. Consult the service-specific documentation for each tool
4. Contact support with connection details and error messages

Security Considerations

Data Privacy

• StackPilot only accesses data necessary for incident analysis
• Sensitive data filtering can be configured per integration
• All data transmission uses TLS encryption
• Data retention follows your configured policies

Access Control

• Use principle of least privilege when granting permissions
• Regularly audit connected services and their access levels
• Revoke access for unused or deprecated integrations
• Monitor API usage patterns for anomalies

By properly configuring your connections, StackPilot can provide comprehensive, intelligent incident analysis that correlates data across your entire development and operations stack.