Re:PagerDuty Files Confidentially for IPO
by ravedave5 on Tuesday January 15, 2019 @11:14PM
(#18918181)
Having one team on victorOps and the other on Pagerduty I can say that pagerduty has better UI and mobile app. The scheduling UI in vitorOps is a mess.
[ Parent
| on HN ]
Re:PagerDuty Files Confidentially for IPO
by xianb on Wednesday January 16, 2019 @09:26AM
(#18921072)
Perhaps this might be a poor setup on my company's part, but it's awful navigating between teams and finding escalation policies and schedules in PD
Re:PagerDuty Files Confidentially for IPO
by NightMKoder on Wednesday January 16, 2019 @02:45AM
(#18919009)
Have you tried OpsGenie by chance? Their pricing looks attractive, but it is Atlassian (I cant get past how slow Jira is).
Re:PagerDuty Files Confidentially for IPO
by carlivar on Wednesday January 16, 2019 @02:47AM
(#18919015)
Their UI is also a mess. So they'll fit right in at Atlassian.
Re:PagerDuty Files Confidentially for IPO
by mryall on Wednesday January 16, 2019 @08:10PM
(#18927405)
Atlassian PM here - we're working on improving Opsgenie's UI. And also the speed of Jira Cloud. You'll see some significant improvements this year.
Re:PagerDuty Files Confidentially for IPO
by flitzofolov on Wednesday January 16, 2019 @09:40AM
(#18921182)
PD's API is superior as well.
Re:PagerDuty Files Confidentially for IPO
by thanatos_dem on Wednesday January 16, 2019 @11:00AM
(#18921935)
Some design decisions aren’t great. For instance, given a service key (effectively the identifier for the service to page), there is no way to tell if it’s for use in the v1 or v2 API. No identifiers in the key that you can check offline, and nothing in the API that you can check it against. They are just uuid’s with the hyphens removes, which is a sort of bizarre formate. So if you have a service that generates pages with user provided service keys (i.e. any custom integration), you either need users to also specify which API version it’s for, which is prone to errors, or blindly try one API version and then if it fails try the other, which increases complexity.
Not a deal breaker by any means, but indicates to me a relatively inexperienced team designing the APIs.