167
edits
Incident Handling: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
* There's no `?ongoing`, instead for now we can track open incidents by checking for unresolved topics | * There's no `?ongoing`, instead for now we can track open incidents by checking for unresolved topics | ||
* The posting of incidents is less smart (only posting when not posted yet), so in order to prevent an incident from not being reported due to network issues or the likes, a message is posted after an inteval (8 hours for non-critical and lower, 1 hour for critical and above) while the incident has not been acknowleged. | * The posting of incidents is less smart (only posting when not posted yet), so in order to prevent an incident from not being reported due to network issues or the likes, a message is posted after an inteval (8 hours for non-critical and lower, 1 hour for critical and above) while the incident has not been acknowleged. | ||
* Incidents can be manually tracked by creating a topic by hand and reporting the problem | * Incidents can be manually tracked by creating a topic by hand and reporting the problem. | ||
* There is no automatic gitlab issue creation or syncing anymore. | * There is no automatic gitlab issue creation or syncing anymore. | ||