You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question regarding incident management: why must every incident be linked to a deployment? I’ve noticed in the documentation that incidents are linked to deployments, but not all incidents are directly caused by deployments. For instance, major cloud outages, human errors, or infrastructure changes can also trigger incidents.
We currently use Jira, where we can set up one board for deployment-related incidents and another for other types of incidents. However, the challenge arises with PagerDuty, which automatically routes incidents to DevLake regardless of their cause.
Does anyone have tips or suggestions on how to manage incidents that aren’t directly linked to deployments effectively?
Thank you.
Screenshots
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Question
Hi everyone,
I hope you’re all doing well.
I have a question regarding incident management: why must every incident be linked to a deployment? I’ve noticed in the documentation that incidents are linked to deployments, but not all incidents are directly caused by deployments. For instance, major cloud outages, human errors, or infrastructure changes can also trigger incidents.
We currently use Jira, where we can set up one board for deployment-related incidents and another for other types of incidents. However, the challenge arises with PagerDuty, which automatically routes incidents to DevLake regardless of their cause.
Does anyone have tips or suggestions on how to manage incidents that aren’t directly linked to deployments effectively?
Thank you.
Screenshots
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: