Tuning Accuracy

guided tour · part 5 of 5 resolve overview docid\ ctmycol8s0io8g1giztix → connect an integration docid\ ig yfnpcmge2yt3oq5i4b → team knowledge docid\ d5xhezjtrrw k5spbvoob → auto investigations docid 3moxjnu2unbupnw evgda → tuning accuracy improving investigation accuracy is an iterative loop give feedback, find the gap, update knowledge or integrations, then re run and compare this final part of the guided tour walks through that loop start with an investigation whose root cause you know pick an investigation where you're certain of the real root cause — ideally an older auto investigated docid 3moxjnu2unbupnw evgda alert you've already diagnosed if you don't know the true answer, you can't tell whether tuning moved resolve closer to it for example, a cpu utilization high alert you've seen before step 1 give feedback open the investigation report and use the thumbs up / thumbs down control if the root cause docid\ ctmycol8s0io8g1giztix matches what you expected, give it a thumbs up and note why if it's wrong, give it a thumbs down and describe the problem — for example, "the root cause looks incorrect because…" feedback does two things it records the outcome so resolve can learn from it, and it lets you track this investigation as you iterate all feedback is visible later under analytics → feedback , where you can see every thumbs up and thumbs down across your investigations step 2 find the gap when an investigation misses, there are usually only a few causes a missing integration — resolve didn't have access to a data source it needed review what's connected in integrations docid\ kj5ntyk6ffniia ux1zuv and add what's missing via connect an integration docid\ ig yfnpcmge2yt3oq5i4b a bad or mis scoped query — for example, resolve queried the wrong log index missing guidance — resolve needs more direction on how to investigate this alert or how to use an integration step 3 update knowledge or integrations go to the relevant team's team knowledge docid\ d5xhezjtrrw k5spbvoob and fill the gap add a sample log query or note the correct index so resolve queries the right place see alert runbooks docid\ ejosivxhatgxk4mm4ngbd add or refine dashboard guidance , docs , or a skill docid\ nlilpthw611fjeawk8o0k that encodes the right procedure if a data source was missing, connect it — see setup & integrations docid\ l dvy9zmbcainld03tvk the full menu of what you can adjust is in the knowledge setup guide docid\ ejosivxhatgxk4mm4ngbd step 4 re investigate and compare back on the investigation report, open the ⋯ menu and choose reinvestigate alert (use the default option) resolve re runs the same alert with your updated knowledge and integrations, so you can compare the new result against the original got a better outcome? give it a thumbs up to lock in the win still off? thumbs down, refine again, and re run repeat this loop — feedback → find the gap → update → re investigate — and accuracy climbs steadily over time this is the same loop that keeps resolve improving long after onboarding you've completed the guided tour 🎉 you now know how to interact with resolve, teach it your systems, automate investigations, and tune them for accuracy where to go next wire up the rest of your stack in setup & integrations docid\ l dvy9zmbcainld03tvk explore the full features docid 53u1g03ypksugnlkwqliy set, including mitigation actions docid\ zlnb3zb3vezbe1qelhgbi and tasks docid\ l mb8qpnclkejs8bfhkud build on resolve with the developers docid\ o vqioqmxfbd4rhujdhq tools — plugins docid\ bcqpoqdctungseqk8q5m , the mcp server docid\ brcq0muxkokd9 cyxb1eb , and the rest api docid 84w41k1clcddxcqw3tihd previous part 4 — auto investigations docid 3moxjnu2unbupnw evgda