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

171–180 of 194 posts

Re: PagerDuty S-1

#171

Post by ody4242 »

jvagner wrote: post #132
eeeeeeeeeeeee wrote: post #88

Earlier quoted context omitted.

How much can it really change though? It’s a fairly simple concept. I always considered the cost is paying for trust and reliability. I know a text message might fail. I want those alert redundancies and I don’t want to have to create that system. I tried some of the competitors out to reduce cost, but UX was definitely lacking (opsgenie for example). We stuck with PagerDuty. That being said, as a potential investor,…

The last time I looked at PagerDuty (a while ago) it didn't have any kind of "calling tree" equivalent for validated notification escalations. Couldn't really see how that could be true, so I'm assuming I didn't understand the product.

We use multiple schedules with Pagerduty, and when an escalation policy is triggered, it can route to multiple additional schedules. So let's say you can escalate to an SME schedule, if a certain incident is not resolved within a certain amount of time.

They have a configuration tab for "business services", where you can set up dependencies between services, but we're not using that, so idk how smart is that.

Re: PagerDuty S-1

#172

Post by isatty »

ec109685 wrote: post #150

PagerDuty is super expensive. With Slack or another messaging app, you just need a system that will support a schedule and route to engineers appropriately as well as post to the slack channel. A lot of the bells and whistles they have aren't useful. Engineers never need to actually use the Pager Duty website and only use the app for ack'ing the page or just do that in Slack. This feels like it should be more of a co…

SRE at a large software company here - PagerDuty is absolutely critical to our operations. I will absolutely not trust Slack's availability nor is Slack the right platform to manage this and to expect immediate responses, even from oncalls.

When you've lots of users bells and whistles like schedule layers and setting overrides are very useful.

You don't need the $99/month plan, you can do fine on $39/month.

Re: PagerDuty S-1

#173

Post by jfk13 »

AJ007 wrote: post #157
eeeeeeeeeeeee wrote: post #92

Earlier quoted context omitted.

I swear half the time my Slack notifications don’t go off on my phone. Even with background refresh on. I would never trust that service for critical alerts. As in, you need to wake up and fix this now. I’ve run my own monitoring solutions. My own Asterisk systems. Even my own Twilio integrations. You are grossly oversimplifying what is needed to create and maintain those systems. For many, PagerDuty is absolutely wo…

Slack notification delivery is definitely not what it used to be.

You mean to say it's slacking off?

Re: PagerDuty S-1

#174

Post by damagednoob »

awakeasleep wrote: post #154
ec109685 wrote: post #150

PagerDuty is super expensive. With Slack or another messaging app, you just need a system that will support a schedule and route to engineers appropriately as well as post to the slack channel. A lot of the bells and whistles they have aren't useful. Engineers never need to actually use the Pager Duty website and only use the app for ack'ing the page or just do that in Slack. This feels like it should be more of a co…

What industry are you in where you care about getting paged after hours, but you're happy tying your paging to Slack's availability, and you have the engineering time to devote to recreating and maintaining a paging system? I'm sure there are industries where that makes sense, but I bet you can imagine there are industries and companies where that doesn't add up.

I haven't created my own paging system but I've gotten quite far with Zabbix and Twilio. Zabbix's feature set includes the ability to define teams and schedules and execute a custom command when downtime is detected.

That being said, I was happy to hear that my new work had a PagerDuty account because the fewer things I have to host and maintain the better.

Re: PagerDuty S-1

#175

Post by skinnymuch »

teej wrote: post #71
throwawaykings wrote: post #38

This makes them probably the second ever YC company to go public, the first being Dropbox. Also related: https://news.ycombinator.com/item?id=758653

Super quick napkin math on YC's investment. Many of these assumptions will be wrong. YC investment: $120,000 [0] YC shares: 1,050,000 [1] PD market cap: $1.3 billion [2] PD share price: $20.23 YC investment value: $21.25 million YC ROI: 175x This is a ~4x return on the S10 batch. In that same batch you have Stripe, which looks like it could be a 3000x+ return for YC. Notes [0] - This could be less, I don't remember t…

Thanks for this! Love to see quick math.

How do you account for dilution though? I’m not too familiar with how it all works, but in this case does it not matter because the amount of shares stays the same? Only total shares have changed?

And yeah Stripe will be a crazy multiplier that has to be at least 2000x and could be over 3000x like you said. I’m guessing they never sold any shares. Especially seeing Square’s market cap above $30B and PayPal at $120B.

Re: PagerDuty S-1

#176

Post by ec109685 »

awakeasleep wrote: post #154
ec109685 wrote: post #150

PagerDuty is super expensive. With Slack or another messaging app, you just need a system that will support a schedule and route to engineers appropriately as well as post to the slack channel. A lot of the bells and whistles they have aren't useful. Engineers never need to actually use the Pager Duty website and only use the app for ack'ing the page or just do that in Slack. This feels like it should be more of a co…

What industry are you in where you care about getting paged after hours, but you're happy tying your paging to Slack's availability, and you have the engineering time to devote to recreating and maintaining a paging system? I'm sure there are industries where that makes sense, but I bet you can imagine there are industries and companies where that doesn't add up.

You still need something like PagerDuty, OpsGenie, etc. for the on call rotation and routing. All I am saying is all the other 1000 features they offer and charge for aren’t needed when you don’t really use their web site at all.

Re: PagerDuty S-1

#177

Post by ec109685 »

isatty wrote: post #172
ec109685 wrote: post #150

PagerDuty is super expensive. With Slack or another messaging app, you just need a system that will support a schedule and route to engineers appropriately as well as post to the slack channel. A lot of the bells and whistles they have aren't useful. Engineers never need to actually use the Pager Duty website and only use the app for ack'ing the page or just do that in Slack. This feels like it should be more of a co…

SRE at a large software company here - PagerDuty is absolutely critical to our operations. I will absolutely not trust Slack's availability nor is Slack the right platform to manage this and to expect immediate responses, even from oncalls. When you've lots of users bells and whistles like schedule layers and setting overrides are very useful. You don't need the $99/month plan, you can do fine on $39/month.

I didn’t say replace the “operator” part of PagerDuty — you still need something to manage on call rotations and escalate to right engineers. But that shouldn’t cost $39 a month per engineer and all the other features won’t be used because people spend most time in their messaging app triaging issues.

Re: PagerDuty S-1

#178

Post by ec109685 »

motakuk wrote: post #169
ec109685 wrote: post #150

PagerDuty is super expensive. With Slack or another messaging app, you just need a system that will support a schedule and route to engineers appropriately as well as post to the slack channel. A lot of the bells and whistles they have aren't useful. Engineers never need to actually use the Pager Duty website and only use the app for ack'ing the page or just do that in Slack. This feels like it should be more of a co…

Exactly why we are building https://amixr.io Schedules, lifecycle, routing in Slack.

Still $29 a month though…

Re: PagerDuty S-1

#179

Post by toomuchtodo »

gaadd33 wrote: post #163
toomuchtodo wrote: post #141

Earlier quoted context omitted.

Unlikely, either because of guarantees (student) or too small (auto loans). It’ll be the corporate bond market getting spooked, and a crunch when anyone running on cheap debt can’t service or refi it without default.

US auto loans have a total of 1.1 trillion outstanding, writing that off wouldn't affect the markets at all or increase the cost of debt?

That collateral is easily repo’d and disposed of. Think Rent A Center. The margins on the vehicles being sold make up for estimated losses.

Re: PagerDuty S-1

#180

Post by robbiemitchell »

ec109685 wrote: post #150

PagerDuty is super expensive. With Slack or another messaging app, you just need a system that will support a schedule and route to engineers appropriately as well as post to the slack channel. A lot of the bells and whistles they have aren't useful. Engineers never need to actually use the Pager Duty website and only use the app for ack'ing the page or just do that in Slack. This feels like it should be more of a co…

Why are you citing the enterprise plan if your argument is that you don’t need most of what they offer?

It’s $30/month for lowest tier with more than 6 users. There’s no way it’s ROI positive for you to build and maintain this yourself until you have [many] hundreds of employees using PD.

The fact that it’s super simple to use while being highly configurable and reliable is a pro, not a con.

Post reply on HN