Contents

# Title

<!--
The title should be the name of the alert (e.g., Generic Alert_AlertTooGeneric).
-->

# Overview

<!--
Address the following:

* What does this alert mean?
* Is it a paging or an email-only alert?
* What factors contributed to the alert?
* What parts of the service are affected?
* What other alerts accompany this alert?
* Who should be notified?
-->

# Alert Severity

<!--
Indicate the reason for the severity (email or paging) of the alert and the
impact of the alerted condition on the system or service.
-->

# Verification

<!--
Provide specific instructions on how to verify that the condition is ongoing.
-->

# Troubleshooting

<!--

List and describe debugging techniques and related information sources.
Include links to relevant dashboards. Include warnings.

Address the following:

* What shows up in the logs when this alert fires?
* What debug handlers are available?
* What are some useful scripts or commands?
* What sort of output do they generate?
* What are some additional tasks that need to be done after the alert is resolved?

-->

# Solution

<!--

List and describe possible solutions for addressing this alert.

Address the following:

* How do I fix the problem and stop this alert?
* What commands should be run to reset things?
* Who should be contacted if this alert happened due to user behavior?
* Who has expertise at debugging this issue?

-->

# Escalation

<!--

List and describe paths of escalation.
Identify whom to notify (person or team) and when.
If there is no need to escalate, indicate that.

-->

# Related Links

<!--

Provide links to relevant related alerts, procedures, and overview documentation.

-->

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
jive-0.7.0	lib/jive/templates/play_book.md