# <Application/Service Name> Runbook#

This document provides information on how to administer our <app/service name> deployment.

## Key Locations#

Env

Namespace

GitHub Repo

Prod

namespace deployed

## Monitoring#

Provide all the important monitoring information related to the application such as links to dashboards, metrics etc.

### Dashboards#

Links to the monitoring dashboards for this service.

Grafana Dashboard

Dashboard Description

dashboard URL

description/purpose of dashboard

### Smoke Test#

Verify that the service is up and available by checking if you can access/login to the service endpoint.

### Health Checks#

How is the health of the service and its dependencies?

## Contact Info#

Team contact info. Potentially contact info for who to escalate to. What services do we have dependencies on? How do we escalate to them? Define this information here.

Primary SME

Secondary SME

Contact

Chat Channel

Name

Name

mailto:name@email.com

gchat/slack channel

## Prerequisites#

List all the prerequisites for managing/deploying the application/service.

## Deployment#

Mention the deployment instructions and how the changes to manifest files are tracked.

Include relevant information pertaining to administrating the service.

## Common Problems#

The following is a list of common issues we’ve encountered with <app/service name> and how to fix them.

### Problem 1#

Describe the issue and provide details as to how this issue is triggered. Include all the necessary steps required for resolving the issue. Fill out the following applicable sections pertaining to the issue.

For Every Alert there should be a corresponding section in alphabetical order

Alert Description: Why do we have this alert? What does it mean? What is typically the cause of this alert?

##### Impact to Customers:#

How does this situation impact our customers? If the customers are not being impacted, this is a good indicator that the alert can be deleted.

#### Remediation Steps:#

Checklist manifesto style steps for how to resolve this alert. A person who has never worked on our stack should be able to follow these steps and remediate the incident. If it cannot be remediated, include escalation steps here.

1. Do this

2. Check this graph

3. Do this thing

4. Do this other thing

5. Verify service has recovered