HN Explorer

10 comments

[ 3.0 ms ] story [ 34.6 ms ] thread
ravedave5
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.
NightMKoder
Have you tried OpsGenie by chance? Their pricing looks attractive, but it is Atlassian (I cant get past how slow Jira is).
carlivar
Their UI is also a mess. So they'll fit right in at Atlassian.
mryall
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.
xianb
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
flitzofolov
PD's API is superior as well.
thanatos_dem
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.