We're interested in understanding how we can auto push next steps of discovery, investigation and exploration when an incident is raised.
We are particularly interested in understanding what data signals in an incident ticket, would be used to come up with suggestions and recommendations.
From what I’ve seen so far, Rovo mainly relies on the core signals already present in the incident ticket to drive its triage suggestions. Things like the summary, description, tags/labels, service or component links, and any priority/severity fields tend to be the strongest indicators. If your team uses structured fields like impacted services, environment (prod/stage), or incident category, those help Rovo narrow down the next recommended steps much more accurately
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.