Skip to content

Commit 40b7ab3

Browse files
data-piratedata-pirate
authored
Add resolve timer in quick links (#58)
2 parents 6cc8f1d + 3d1927b commit 40b7ab3

File tree

2 files changed

+172
-0
lines changed

2 files changed

+172
-0
lines changed

‎SUMMARY.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@
1717
* [Sharing incidents](incidents/sharing-incidents.md)
1818
* [Why does message parsing fail?](incidents/why-does-message-parsing-fail.md)
1919
* [Rate limiting on duplicate incidents](incidents/rate-limiting-on-duplicate-incidents.md)
20+
* [Setting up Resolve timer](incidents/resolve-timer-for-incidents.md)
2021

2122
## Alerts
2223

‎incidents/resolve-timer-for-incidents.md‎

Lines changed: 171 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,171 @@
1+
# Resolve Timer
2+
3+
Keep your incident dashboard clean and focused with automated incident resolution. Resolve Timer automatically closes incidents after a specified time period, helping your team focus on what matters most.
4+
5+
## Overview
6+
7+
Resolve Timer is an intelligent automation feature that automatically resolves incidents after a predetermined time period. Think of it as your dashboard's cleanup crew - it ensures that incidents don't linger indefinitely and clutter your incident management view.
8+
9+
When an incident remains open for the duration you've specified, Resolve Timer steps in and automatically marks it as resolved. This helps maintain a clean, actionable dashboard where your team can focus on active, unresolved incidents that need immediate attention.
10+
11+
## Why use Resolve Timer?
12+
13+
**Cleaner dashboards**: Eliminate incident clutter and maintain focus on active issues that require immediate attention.
14+
15+
**Better team productivity**: Your team spends time on genuine incidents.
16+
17+
**Consistent incident hygiene**: Ensure incidents don't remain open indefinitely, maintaining accurate incident metrics and reporting.
18+
19+
## How Resolve Timer works
20+
21+
Once configured, Resolve Timer monitors your incidents and automatically resolves them based on your specified timeframe. The timer starts counting from the moment an incident is created, and when it reaches your configured duration, the incident is automatically marked as resolved.
22+
23+
You can configure Resolve Timer in two ways:
24+
- **Integration-level**: Automatically resolve all incidents from a specific integration
25+
- **Alert rule-level**: Resolve incidents that match specific conditions using alert rules
26+
27+
## Prerequisites
28+
29+
Before configuring Resolve Timer, make sure you have:
30+
- Permission to Edit/Create an Alert rule
31+
- Permission to Edit/Create an Integration
32+
33+
## Configuration Methods
34+
35+
### Method 1: Integration-level Resolve Timer
36+
37+
Use this method when you want every incident from a specific integration to automatically resolve after a set time period.
38+
39+
#### Step-by-step setup
40+
41+
**Step 1**: Navigate to your integration settings
42+
- Go to **Integrations** in your Spike dashboard
43+
- Find the integration you want to configure
44+
- Click **Edit** or create a new integration
45+
46+
**Step 2**: Access advanced configuration
47+
- Scroll down to the **Advanced Configuration** section
48+
- Look for the **Resolve Timer** toggle switch
49+
50+
**Step 3**: Enable and configure Resolve Timer
51+
- Toggle the **Resolve Timer** switch to **ON**
52+
- Enter your desired time value in the input field
53+
- Select the time unit from the dropdown: **Minutes**, **Hours**, or **Days**
54+
55+
**Step 4**: Save your configuration
56+
- Click **Save** to apply your changes
57+
- All future incidents from this integration will automatically resolve after your specified time period
58+
59+
#### Example configuration
60+
- **Time value**: 24
61+
- **Time unit**: Hours
62+
- **Result**: All incidents from this integration will automatically resolve after 24 hours
63+
64+
![How to configure resolve timer in alert rules](../.gitbook/assets/setup%20resolve%20timer%20(integration).png)
65+
66+
### Method 2: Alert Rule-based Resolve Timer
67+
68+
Use this method when you want to resolve incidents that match specific conditions, giving you more granular control over which incidents get automatically resolved.
69+
70+
#### Step-by-step setup
71+
72+
**Step 1**: Create or edit an alert rule
73+
- Navigate to **Alert Rules** in your dashboard
74+
- Click **Create Alert Rule** or select an existing rule to edit
75+
76+
**Step 2**: Configure your conditions
77+
- Set up your alert conditions as needed
78+
- Define which incidents should trigger this rule
79+
80+
**Step 3**: Add the Resolve Timer action
81+
- In the **Actions** section, click **Add Action**
82+
- Select **Resolve After** from the action dropdown
83+
84+
**Step 4**: Configure timing
85+
- Enter your desired time value
86+
- Select the time unit: **Minutes**, **Hours**, or **Days**
87+
- Click **Save** or **Update** to apply your rule
88+
89+
#### Example alert rule configuration
90+
- **Condition**: Incidents from "Production Database" service
91+
- **Action**: Resolve After 2 hours
92+
- **Result**: Database incidents automatically resolve after 2 hours if not manually handled
93+
94+
![How to configure resolve timer in alert rules](../.gitbook/assets/Setup%20resovle%20timer%20(alert%20rules).png)
95+
96+
## Configuration Options
97+
98+
### Time Units Available
99+
| Unit | Minimum Value | Maximum Value | Best For |
100+
|------|---------------|---------------|----------|
101+
| Minutes | 1 | 1440 (24 hours) | Short-lived alerts, testing |
102+
| Hours | 1 | 168 (7 days) | Standard incident workflows |
103+
| Days | 1 | 7 | Long-running maintenance, planned outages |
104+
105+
### Integration vs Alert Rule: Which to choose?
106+
107+
**Use Integration-level Resolve Timer when**:
108+
- You want consistent behavior across all incidents from a source
109+
- You're dealing with noisy integrations that generate many low-priority alerts
110+
- You need simple, set-and-forget automation
111+
112+
**Use Alert Rule-based Resolve Timer when**:
113+
- You need different resolution times based on incident characteristics
114+
- You want to combine auto-resolution with other automated actions
115+
- You need conditional logic for incident resolution
116+
117+
118+
> ✅ **Resolve Timer is available on all Spike plans** - Starter, Business, and Enterprise.
119+
120+
## Best Practices
121+
122+
**Start with longer timeframes**: Begin with conservative resolution times (like 24 hours) and adjust based on your team's workflow patterns.
123+
124+
**Monitor resolution patterns**: Review auto-resolved incidents periodically to ensure you're not missing important alerts.
125+
126+
**Use different timers for different services**: Critical production services might need longer resolution times than development or staging environments.
127+
128+
**Test your configuration**: Set up Resolve Timer with a test integration first to understand how it behaves with your incident types.
129+
130+
## FAQs
131+
132+
<details>
133+
<summary>Q: Can I disable Resolve Timer for specific incidents?</summary>
134+
A: Not for individual incidents, but you can disable it at the integration level or modify alert rule conditions to exclude certain incident types.
135+
</details>
136+
137+
<details>
138+
<summary>Q: What happens if I manually resolve an incident before the timer expires?</summary>
139+
A: Manual resolution takes priority. The timer stops, and the incident remains manually resolved.
140+
</details>
141+
142+
<details>
143+
<summary>Q: Can I see which incidents were auto-resolved?</summary>
144+
A: Yes, auto-resolved incidents show a `Resolved (timer)` status. You can also check activity log to see if the incident was auto
145+
</details>
146+
147+
<details>
148+
<summary>Q: Can I set different resolution times for different severity levels?</summary>
149+
A: Yes, using alert rules you can create different Resolve Timer configurations based on incident severity, service, or other conditions.
150+
</details>
151+
152+
<details>
153+
<summary>Q: What's the shortest resolution time I can set?</summary>
154+
A: The minimum is 1 minute, though we recommend at least 15-30 minutes for most use cases to allow for proper incident handling.
155+
</details>
156+
157+
<details>
158+
<summary>Q: Will I get notified when incidents auto-resolve?</summary>
159+
A: This depends on your notification settings. You can configure whether you want to receive notifications for auto-resolved incidents.
160+
</details>
161+
162+
## Need Help?
163+
164+
If you're having trouble setting up Resolve Timer or have questions about your specific use case:
165+
- Check out our [Integration documentation](https://docs.spike.sh/integrations-guideline/create-integration-and-service-on-dashboard)
166+
- Learn about [Alert Rules](https://docs.spike.sh/alerts/alert-rules) for advanced incident handling
167+
- Contact our support team at [email protected] for personalized assistance
168+
169+
---
170+
171+
*Was this helpful? Let us know at [email protected]*

0 commit comments

Comments
 (0)