[HN Gopher] My big fat monolithic alert
       ___________________________________________________________________
        
       My big fat monolithic alert
        
       Author : kiyanwang
       Score  : 24 points
       Date   : 2022-06-05 09:54 UTC (13 hours ago)
        
 (HTM) web link (cherkaskyb.medium.com)
 (TXT) w3m dump (cherkaskyb.medium.com)
        
       | abdouls wrote:
       | I agree with the ownership part. As part of my team (devops), we
       | try our best to help with alerts and incidents, however, without
       | ownership we are limited.
       | 
       | We do not know a product or a component better than those who own
       | it or code it.
        
       | rowan_mcd wrote:
       | Very familiar with this problem. This process has happened at my
       | last job and is just starting at my current job. Distributing the
       | issues by team makes a ton of sense, but in my experience, it
       | only gets so far. It's always been unclear how to handle, and
       | scale, the remaining 10% of on call burden.
        
       | mijoharas wrote:
       | Is there a definition for the "NOC" acronym that the author uses
       | throughout? I can't see one, and it's not immediately clear from
       | context to me.
        
         | mikequinlan wrote:
         | Network Operations Center
        
         | jandrewrogers wrote:
         | From context, I think it might be Network Operations Center,
         | which was a common acronym at one time.
        
         | x0x0 wrote:
         | network operations center
        
         | [deleted]
        
       | afandian wrote:
       | I do wish posts like this had absolute numbers (or did I miss
       | some?). Is this a monolith served by a team of 5, 15 or 50?
        
       ___________________________________________________________________
       (page generated 2022-06-05 23:02 UTC)