Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PagerDuty S-1

sec.gov

Post reply on HN
Print view View original

101–110 of 194 posts

Re: PagerDuty S-1

#101

Post by evrydayhustling »

teej wrote: post #2

> If we fail to offer high-quality support, our business and reputation could suffer. I don't know how common this is in S-1 filings but it stuck out to me. Support is often viewed as a cost center, I love that PagerDuty makes it such a high priority. Edit: After some research, it turns out this is common. Docusign, Dropbox, Okta, Zuora, and MongoDB all have this statement exactly or similar.

More and more companies are also involving PagerDuty in their support! Incidents and multichannel escalation are great complements to standard support workflows for high impact cases.

Re: PagerDuty S-1

#102

Post by cm2012 »

disiplus wrote: post #98
cm2012 wrote: post #94

Earlier quoted context omitted.

I can guarantee you it can work for B2B at scale. I've personally grown multiple B2B accounts from $0 to an ROI positive six figures monthly. From seed stage start-ups to post IPO companies. That's not to say you did anything wrong - it's possible your specific set-up wouldn't work. But many agencies do not know how to do it.

how is that measured ?. initially we thought, how stupid we where in not paying for facebook earlier because of increase in signups. but on closer look the registrations all where from private individuals (remember we are b2b) and they would never fill out the data about the company or even log again after initial signup. even those that where registered as companies never used it. i think facebook user has a differe…

Measured by revenue generated per $ spent. What works depends on your specific situation.

Re: PagerDuty S-1

#103

Post by caprese »

umeshunni wrote: post #6

2017: $79.6M revenue, ($38M)in losses. 9 months of 2018: $84M revenue, ($34.5M) in losses. Costs seem generally under control except the significant growth (+66%) in G&A expenses. Why the hurry to IPO?

> Why the hurry to IPO?

ITT: "A profitable tech company going public while there is still growth potential? Is this a scam?"

Aside from the liquidity and valid option of getting a funding round from underwriters has this seriously become a foreign concept in this market?

Re: PagerDuty S-1

#104

Post by mamurphy »

lozenge wrote: post #50
jessemillar wrote: post #20

Earlier quoted context omitted.

Out of genuine curiosity, do you have a list of good alternatives or some reading material on "paging" best practices? My team uses PagerDuty but I've never really questioned if there's a better method out there because the system PagerDuty replaced for us was so terrible that PagerDuty seemed like a godsend.

Google's free SRE handbook has some info.

I don't see alternative services on this page (https://landing.google.com/sre/sre-book/chapters/monitoring-...) Do you have any alternates you would recommend?

Re: PagerDuty S-1

#105

Post by dharmab »

0xffff2 wrote: post #86
dharmab wrote: post #65

Earlier quoted context omitted.

When I call my insurance or bank, I get a pleasant voice interface. When PagerDuty calls my carphone (or worse, my motorcycle helmet communicator), I get an inhuman civil defense robot from 1980 that only accepts touch-tone inputs.

I wish I could opt in to that for all automated communications. Fighting my way through voice-recognition menus is always a pain in the ass that makes me wish for the telephone menu systems of the 90s.

I like having both options!

Re: PagerDuty S-1

#106

Post by phxrsg »

whalesalad wrote: post #23
trimbo wrote: post #21

Earlier quoted context omitted.

They're spending $30M+ on R&D, so if you feel that way as a customer, that's not good.

On principle alone I wouldn't give them my money ever again. I'd engineer my own lightweight solution before then or use an underdog competitor. I have a sour taste in my mouth for their meteoric rise to success/IPO versus their pathetic investments (or lack therof) in product improvement. It really sucks to use. Reminds me of Engineyard (also abandonware).

Honestly, if your response to critical ops notifications is to engineer a lightweight solution as a part time pet project, I don't want to work for or use your product.

If you are talking instead about hiring an ops engineer to build your custom lightweight solution, I would ask why you're spending 100k+ all-in cost on an engineer to do something you could pay PD to do for cheaper.

Re: PagerDuty S-1

#108

Post by gmjosack »

ttul wrote: post #75
dharmab wrote: post #65

Earlier quoted context omitted.

When I call my insurance or bank, I get a pleasant voice interface. When PagerDuty calls my carphone (or worse, my motorcycle helmet communicator), I get an inhuman civil defense robot from 1980 that only accepts touch-tone inputs.

But, it absolutely never fails.

This is not true in my experience. I led the monitoring team at my past job and we spent a non significant effort monitoring PagerDuty due to often delays in ingestion and notification. If you page through their status page[1] they have a problem with delayed ingestion or notification almost monthly. If people actually monitored they'd be surprised how often they miss SLA.

[1] https://status.pagerduty.com/history?page=1

Re: PagerDuty S-1

#109

Post by quickthrower2 »

jedberg wrote: post #95
dtehranian wrote: post #87

Earlier quoted context omitted.

> Signs all point to a recession in one to two years. People have been saying this for the past 7 years.

Maybe, but people who actually know what they're talking about have only been saying it recently.

What's the trigger?

Re: PagerDuty S-1

#110

Post by hacker_newz »

thanatos_dem wrote: post #28

I run a service that integrates with pager duty on behalf of our users, and man oh man did they make some poor design choices with their API. The most glaring one is their integration keys, which is how you trigger an alert. They’re just v4 uuids with the hyphens removed, or in other words, completely random. This is fine by itself, except they have two versions of their event API, and keys for the v1 API don’t work…

You do realize the v1 API was deprecated last year?
Post reply on HN