infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Thistlethwaite (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-16523) Duplicated entry on status page
Date Wed, 04 Jul 2018 02:28:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-16523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Thistlethwaite resolved INFRA-16523.
------------------------------------------
    Resolution: Won't Fix  (was: Fixed)

Found out that this dupe is created if more than one person acks the page through PagerDuty.
There's nothing we can do about this as PagerDuty just fires off dupe API calls. PagerDuty
has the info on who ack and responded to the page, while that gets passed to Statuspage, the
team didn't want their info pasted all over twitter, etc for every page.



> Duplicated entry on status page
> -------------------------------
>
>                 Key: INFRA-16523
>                 URL: https://issues.apache.org/jira/browse/INFRA-16523
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Outages
>            Reporter: Sebb
>            Assignee: Chris Thistlethwaite
>            Priority: Trivial
>
> There is a duplicated entry on the status.a.o page:
> ====================
> Build Services https://ci.apache.org/ is down!
> Subscribe
> Update - The page has been acknowledged and we're on the case. PD incident number 2392
PD incident https://apache.pagerduty.com/incidents/PTIS3LT
> May 14, 16:05 UTC
> Update - The page has been acknowledged and we're on the case. PD incident number 2392
PD incident https://apache.pagerduty.com/incidents/PTIS3LT
> May 14, 16:05 UTC
> Investigating - Infra has been paged. /pd ack 2392 PD incident https://apache.pagerduty.com/incidents/PTIS3LT
> May 14, 16:05 UTC
> ====================
> Note that the first two entries have the identical text.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message