PagerDuty Files Confidentially for IPO(bloomberg.com)

28 pointsby J253vor 8 Jahren9 comments

https://www.bloomberg.com/news/articles/2019-01-15/software-maker-pagerduty-is-said-to-file-confidentially-for-ipo

10 comments

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.

xianbvor 8 Jahren

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

NightMKodervor 8 Jahren

Have you tried OpsGenie by chance? Their pricing looks attractive, but it is Atlassian (I cant get past how slow Jira is).

carlivarvor 8 Jahren

Their UI is also a mess. So they'll fit right in at Atlassian.

mryallvor 8 Jahren

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.

flitzofolovvor 8 Jahren

PD's API is superior as well.

thanatos_demvor 8 Jahren

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.

romanhnvor 8 Jahren

Worth recalling that PagerDuty is a YC S10 alumnus. https://news.ycombinator.com/item?id=758653

DeonPennyvor 8 Jahren

YC raking it in this year

TagAsDelusionvor 8 Jahren