Knowledge Base

Issues

Communicating with your audience about service issues can be difficult, a status page should make this process easy for your team. The Issues section of your Hund status page dashboard helps you communicate about ongoing or scheduled issues.

Creating an Issue

Title

The title of an issue should describe a component's incident in a few words. Leave the scope of the incident out of the title, as your status page provides this information already (i.e. prefer "DDoS Mitigation" over "Website DDoS Mitigation").

Labels

Both issues and issue updates have labels. Labels can be thought of as the status of an issue since they convey your progress in resolving them. Examples include "investigating", "assessed", "monitoring", and "resolved".

Body

The goal of an issue's body is to minimize incoming support inquiries by providing detailed information. You may want to include helpful details such as the scope of affected users, or estimated time to resolve the incident.

Note: Issues support Markdown!

State Override

Sometimes you may wish to override a component's state while an issue is open. An override is useful, for example, when a payment processor goes down but your service is still functional. Keep in mind that state overrides affect your component's percent uptime as normal status changes from a watchdog would.

Scheduling an Issue

Issues can start and end at specified times for planned service outages (e.g. server maintenance) or other announcements that don't affect availability.

If you would like your users to be notified about upcoming scheduled issues, you can choose to have them notified relative to the starting time.

Updating an Issue

Issue updates provide your audience with information about issue progress (e.g. resolution, investigation, postmortems). Update issues by viewing an individual issue in the dashboard.

Once an issue update uses the "resolved" label, the issue is considered resolved.

Issue Templates

To aid in the speedy creation of issues, we support issue templates for all components. For some components, such as those using the PagerDuty watchdog, issues can be automatically created when the watchdog detects a status change.

We also expose variables (e.g. PagerDuty incidents, component/group names, etc.) in order to help make a single issue template general enough to be used for as many similar components as possible. Your status page's dashboard provides further documentation on setup.