You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by "KelvinVenancio (via GitHub)" <gi...@apache.org> on 2024/05/17 14:13:14 UTC

[I] [Question][Incident] Incident management [incubator-devlake]

KelvinVenancio opened a new issue, #7487:
URL: https://github.com/apache/incubator-devlake/issues/7487

   <!--
   Licensed to the Apache Software Foundation (ASF) under one or more
   contributor license agreements.  See the NOTICE file distributed with
   this work for additional information regarding copyright ownership.
   The ASF licenses this file to You under the Apache License, Version 2.0
   (the "License"); you may not use this file except in compliance with
   the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
   -->
   
   ## Question
   Hi everyone,
   
   I hope you’re all doing well.
   
   I have a question regarding incident management: why is it necessary for every incident to 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 trigger incidents as well.
   
   We currently use Jira, where we could 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 effectively manage incidents that aren’t directly linked to deployments?
   Thank you. 
   
   ## Screenshots
   If applicable, add screenshots to help explain.
   
   ## Additional context
   Add any other context here.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Question][Incident] Incident management [incubator-devlake]

Posted by "KelvinVenancio (via GitHub)" <gi...@apache.org>.
KelvinVenancio closed issue #7487: [Question][Incident] Incident management
URL: https://github.com/apache/incubator-devlake/issues/7487


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org