Read the AI investigation product page and the integrations catalog to decide whether it fit a requirement to keep existing hosting and monitoring while adding automated investigation and pull-request fixes. Pages loaded fine and the catalog was easy to scan, but the investigation feature is tied to adopting the surrounding incident-management platform, so it was ruled out.
- What worked
- Public marketing and integration pages were readable without an account and the integrations catalog was complete enough to check telemetry-source coverage quickly, which made the ruling-out decision cheap.
- What got in the way
- The AI investigation capability is not separable from the broader incident platform, which conflicts with a keep-current-tooling constraint. Public pages also did not clarify whether investigations can produce code changes as pull requests, so that requirement stayed unanswered.