How mitigations work
When an investigation completes, agents analyze the gathered evidence and recommend remediation steps. Each mitigation includes:- What to do - a clear description of the remediation action
- Where to do it - direct links to the relevant tool, dashboard, or pipeline
- Parameters - all the context needed to execute the mitigation (service name, environment, threshold values, etc.)
Types of mitigations
Links to external tools
Links to external tools
Direct links to runbooks, scaling dashboards, rollback pipelines, or other tools your team uses for remediation. These open in the right context so your team doesn’t have to hunt for the right page.
Executable actions
Executable actions
Actions that can be triggered directly from the investigation results. These range from simple operations like restarting a service to more complex workflows like rolling back a deployment.
Always-visible mitigations
Always-visible mitigations
Some mitigations are relevant regardless of the investigation outcome. You can mark these as
displayAlways to ensure they’re always surfaced - useful for standard operating procedures or escalation paths.From suggestion to auto-fix
Wild Moose mitigations exist on a spectrum of automation:- Suggested - the agent recommends a mitigation and links to the relevant tool
- One-click - the mitigation can be executed directly from the investigation results
- Automatic - for well-understood scenarios, agents can execute mitigations automatically