> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/ai-sre/3.0/ai-sre-for-administrators/set-up-runbook-management/triggers/advanced-scenarios.md).

# Best Practices

### Design principles <a href="#design-principles" id="design-principles"></a>

* **Specific conditions:** Create precise trigger conditions to avoid false positives
* **Logical grouping:** Organize related triggers for easier management
* **Performance optimization:** Design efficient conditions that do not overload the system
* **Clear naming:** Use descriptive names that clearly indicate trigger purpose

***

### Operational excellence <a href="#operational-excellence" id="operational-excellence"></a>

* **Avoid trigger overlap:** Ensure multiple runbooks do not trigger simultaneously for the same event
* **Use appropriate delays:** Add delays between related triggers to prevent conflicts
* **Test thoroughly:** Validate trigger conditions in non-production environments first
* **Monitor execution:** Track trigger effectiveness and adjust conditions as needed

***

### Security considerations <a href="#security-considerations" id="security-considerations"></a>

* **Access control:** Ensure triggers have appropriate permissions for their actions
* **Data validation:** Validate all input data before trigger execution
* **Audit logging:** Maintain comprehensive logs of trigger activations
* **Error handling:** Implement robust error handling for failed trigger executions

***

### Multi-condition triggers <a href="#multi-condition-triggers" id="multi-condition-triggers"></a>

Configure complex triggers that respond to multiple conditions:

* **Incident severity and service:** Trigger only for high-severity incidents affecting critical services
* **Time and alert volume:** Activate during business hours when alert volume exceeds thresholds
* **Team assignment and escalation:** Execute when incidents are escalated to specific teams

***

### Conditional execution <a href="#conditional-execution" id="conditional-execution"></a>

Implement smart trigger logic:

* **Environment-specific:** Different triggers for production vs. development environments
* **Service-aware:** Triggers that behave differently based on affected services
* **Context-sensitive:** Triggers that adapt based on incident context and history

***

### Next steps <a href="#next-steps" id="next-steps"></a>

* Go to [Use CEL expressions in runbook triggers](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/triggers/use-cel-triggers.md) to implement complex conditional logic.
* Go to [Create runbook triggers](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/triggers/create-trigger.md) to learn the basics of trigger creation.
* Go to [Troubleshooting triggers](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/triggers/troubleshooting.md) to resolve common issues.