home.social

#pagerduty — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pagerduty, aggregated by home.social.

  1. Walp. I am suddenly looking for work.

    If you know of any remote-friendly places looking for senior software folks, gimme a holler

    #pagerduty #layoffs

  2. Walp. I am suddenly looking for work.

    If you know of any remote-friendly places looking for senior software folks, gimme a holler

    #pagerduty-layoffs

  3. Walp. I am suddenly looking for work.

    If you know of any remote-friendly places looking for senior software folks, gimme a holler

  4. Walp. I am suddenly looking for work.

    If you know of any remote-friendly places looking for senior software folks, gimme a holler

    #pagerduty-layoffs

  5. Walp. I am suddenly looking for work.

    If you know of any remote-friendly places looking for senior software folks, gimme a holler

    #pagerduty-layoffs

  6. #𝐏𝐚𝐠𝐞𝐫𝐃𝐮𝐭𝐲 𝐬𝐮𝐟𝐟𝐞𝐫𝐞𝐝 𝐚 𝐦𝐚𝐣𝐨𝐫 𝐨𝐮𝐭𝐚𝐠𝐞 𝐢𝐧 𝐀𝐮𝐠𝐮𝐬𝐭 𝟐𝟎𝟐𝟓.

    Impact Summary in the US service region:
    🔸 9+ hours of significant service degradation
    🔸 95% of events rejected at peak (38 mins)
    🔸 18% of create requests errored (130 mins)

    🔗 Read more on #InfoQ about the scope of the problem, the customer impact, and how PagerDuty is working to prevent a recurrence ⇨ bit.ly/46rq0f5

    #DevOps #Observability #IncidentResponse

  7. #𝐏𝐚𝐠𝐞𝐫𝐃𝐮𝐭𝐲 𝐬𝐮𝐟𝐟𝐞𝐫𝐞𝐝 𝐚 𝐦𝐚𝐣𝐨𝐫 𝐨𝐮𝐭𝐚𝐠𝐞 𝐢𝐧 𝐀𝐮𝐠𝐮𝐬𝐭 𝟐𝟎𝟐𝟓.

    Impact Summary in the US service region:
    🔸 9+ hours of significant service degradation
    🔸 95% of events rejected at peak (38 mins)
    🔸 18% of create requests errored (130 mins)

    🔗 Read more on #InfoQ about the scope of the problem, the customer impact, and how PagerDuty is working to prevent a recurrence ⇨ bit.ly/46rq0f5

    #DevOps #Observability #IncidentResponse

  8. #𝐏𝐚𝐠𝐞𝐫𝐃𝐮𝐭𝐲 𝐬𝐮𝐟𝐟𝐞𝐫𝐞𝐝 𝐚 𝐦𝐚𝐣𝐨𝐫 𝐨𝐮𝐭𝐚𝐠𝐞 𝐢𝐧 𝐀𝐮𝐠𝐮𝐬𝐭 𝟐𝟎𝟐𝟓.

    Impact Summary in the US service region:
    🔸 9+ hours of significant service degradation
    🔸 95% of events rejected at peak (38 mins)
    🔸 18% of create requests errored (130 mins)

    🔗 Read more on #InfoQ about the scope of the problem, the customer impact, and how PagerDuty is working to prevent a recurrence ⇨ bit.ly/46rq0f5

    #DevOps #Observability #IncidentResponse

  9. #𝐏𝐚𝐠𝐞𝐫𝐃𝐮𝐭𝐲 𝐬𝐮𝐟𝐟𝐞𝐫𝐞𝐝 𝐚 𝐦𝐚𝐣𝐨𝐫 𝐨𝐮𝐭𝐚𝐠𝐞 𝐢𝐧 𝐀𝐮𝐠𝐮𝐬𝐭 𝟐𝟎𝟐𝟓.

    Impact Summary in the US service region:
    🔸 9+ hours of significant service degradation
    🔸 95% of events rejected at peak (38 mins)
    🔸 18% of create requests errored (130 mins)

    🔗 Read more on #InfoQ about the scope of the problem, the customer impact, and how PagerDuty is working to prevent a recurrence ⇨ bit.ly/46rq0f5

    #DevOps #Observability #IncidentResponse

  10. 𝐬𝐮𝐟𝐟𝐞𝐫𝐞𝐝 𝐚 𝐦𝐚𝐣𝐨𝐫 𝐨𝐮𝐭𝐚𝐠𝐞 𝐢𝐧 𝐀𝐮𝐠𝐮𝐬𝐭 𝟐𝟎𝟐𝟓.

    Impact Summary in the US service region:
    🔸 9+ hours of significant service degradation
    🔸 95% of events rejected at peak (38 mins)
    🔸 18% of create requests errored (130 mins)

    🔗 Read more on about the scope of the problem, the customer impact, and how PagerDuty is working to prevent a recurrence ⇨ bit.ly/46rq0f5

  11. Hackers exploited the app to steal OAuth tokens and access Salesforce data, exposing customer details at Palo Alto Networks, Zscaler, and PagerDuty.

    Read: hackread.com/palo-alto-network