Connect Integrations

this guide walks you through connecting resolve ai 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 resolve ai account ( 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 resolve ai for your environment , you'll name your organization colleagues with the same email domain can automatically join this organization once it's created name your organization 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 observability logs, metrics, dashboards, traces, alerts code git integration infrastructure aws, gcp, kubernetes knowledge confluence, notion chat slack, ms teams connect a first integration step 3 configure your integration each integration follows a simple, guided flow let's look at grafana as an example name (e g , prod grafana ) — helps distinguish between multiple instances connection details enter your instance url and relevant credentials (api token or oauth) configure integration need deep technical details? check our https //docs resolve ai/setup and integrations for step by step permissions and troubleshooting for every tool 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 resolve ai 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 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 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