[HN Gopher] Show HN: I am building an open-source incident manag...
       ___________________________________________________________________
        
       Show HN: I am building an open-source incident management platform
        
       I'm building Incidental, an open-source (MIT license) incident
       management platform.  I've been working on it for the past couple
       of months as a hobby, and now it's at a state where I'm comfortable
       sharing it. This is also my first open source project.  Features: -
       Custom roles - Custom severities - Integrated with Slack - Web
       interface  Todos: - Custom fields - Custom workflows  Website:
       https://incidental.dev Github:
       https://github.com/incidentalhq/incidental  I'd love to hear your
       feedback.  Thanks!
        
       Author : sanj001
       Score  : 92 points
       Date   : 2024-07-08 13:34 UTC (9 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | matthewcford wrote:
       | We've been building same thing hope to share it soon.
        
         | dotancohen wrote:
         | Tell us more.
        
       | otabdeveloper4 wrote:
       | > Slack
       | 
       | Thanks but no thanks.
        
         | shahahmed wrote:
         | curious, is this because you expect something other than Slack
         | supported?
        
         | DowagerDave wrote:
         | could be worse... Teams cough, cough
        
       | allywilson wrote:
       | Different auth options (SAML, OAuth, etc.) would be a nice to
       | have. I look forward to the progress on this tool :-)
        
       | novia wrote:
       | I love to see it. Thank you for building this. This is a problem
       | that's been solved many times over by private companies, and they
       | charge other institutions exorbitant fees for the privilege of
       | using their software. I hope you can get many companies to put
       | skin in the game and contribute towards fixing bugs. It'll be
       | cheaper for them in the long run than paying those external
       | vendors.
       | 
       | For those of you complaining about the slack integration in the
       | comments, you know you can just not connect that, right?
        
         | dewey wrote:
         | > I hope you can get many companies to put skin in the game and
         | contribute towards fixing bugs. It'll be cheaper for them in
         | the long run than paying those external vendors.
         | 
         | This would be a nice world to live in, but unfortunately this
         | is very rarely the case as you can see with most open source
         | projects that are used in many companies and are underfunded
         | and understaffed.
         | 
         | Most bigger companies value saved time of not integrating
         | something themselves, liability and having someone else to call
         | if something goes wrong higher than saving a few thousand bucks
         | a year for some external vendor. Which makes total sense for
         | something that's not your core business.
        
       | Rickasaurus wrote:
       | My pet feature is good and tight Jira (or ticket manager)
       | integration so it opens tickets for the team to put time on,
       | maybe even syncs time? Really nicely streamline so the time to
       | remediate is tracked as part of the team's work.
        
       | vindex10 wrote:
       | I will just share a somewhat similar project:
       | https://github.com/netflix/dispatch
       | 
       | Also open source, also Python, also incident management, also
       | custom severities (but not as much of custom roles, afaik) :) Has
       | some integrations with slack, but not focused on Slack
       | particularly.
       | 
       | Can be a good project to learn from as well :)
       | 
       | My relation to it: I only contributed with a couple of pull
       | requests there :)
        
         | brunoqc wrote:
         | It looks nice. I wish it would support
         | prometheus/lokio/grafana.
        
       | synack wrote:
       | Use the semantics of the standard Incident Command System.
       | Emergency responders have spent decades figuring out the best way
       | to organize for these situations. Tech orgs should leverage that
       | work.
       | 
       | https://en.wikipedia.org/wiki/Incident_Command_System
       | 
       | https://training.fema.gov/nims/
        
         | joseferben wrote:
         | this looks interesting. any first hands experience applying
         | this for tech incidents?
        
           | shahahmed wrote:
           | this is detailed in the Google SRE book:
           | https://sre.google/workbook/incident-response/
        
           | eep_social wrote:
           | I have experience applying ICS-style process to incidents and
           | have delivered training to ~hundreds of engineers at $job. I
           | am partial to this PD doc: https://response.pagerduty.com/tra
           | ining/courses/incident_res...
        
       | jbcranshaw wrote:
       | Just curious, what's the backstory? What inspired you to work on
       | this?
        
       | pinkmuffinere wrote:
       | I love your minimal-but-effective splash page! It looks like it
       | didn't take too long to build, but it shows what the tool looks
       | like and gives a link to waitlist
        
       | nagstler wrote:
       | I'm definitely looking forward to this project!
       | 
       | Have you considered how Incidental might integrate with other
       | open-source tools?
       | 
       | I'd love to use something like this in my OSS project.
       | 
       | https://github.com/Multiwoven/multiwoven
        
       ___________________________________________________________________
       (page generated 2024-07-08 23:01 UTC)