Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question][Incident] Incident management #7487

Closed
KelvinVenancio opened this issue May 17, 2024 · 0 comments
Closed

[Question][Incident] Incident management #7487

KelvinVenancio opened this issue May 17, 2024 · 0 comments
Labels
devops Something about CI/CD (devops) type/question This issue is a question

Comments

@KelvinVenancio
Copy link

KelvinVenancio commented May 17, 2024

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

@KelvinVenancio KelvinVenancio added the type/question This issue is a question label May 17, 2024
@dosubot dosubot bot added devops Something about CI/CD (devops) type/incident labels May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Something about CI/CD (devops) type/question This issue is a question
Projects
None yet
Development

No branches or pull requests

2 participants