[jurajmasar]

At the risk of being banned forever on HN:

<self-promotion>

We built Better Stack (https://betterstack.com/incident-management) after being frustrated with PagerDuty a couple years back. It's a solid place to land if you need to migrate away from Opsgenie.

Let me know at [e-mail] if you have questions, happy to help! (I'm the founder)

</self-promotion>

[sunaden]

We are a very happy customer of better stack - it’s a genuinely great product that did not let us down so far and it’s way more intuitive than my previous experiences with Opsgenie (setting up escalation policies was a nightmare in opsgenie)

We also use the AI features quite a bit, but they can be easily ignored if unwanted

[parliament32]

That's a lot of "AI" -- incident response is the last place I'd want to see AI-anything, other than helping me write post-mortems maybe. Who's liable when your text generator decides to close an impacting incident?

[shric]

Perhaps I'm in the minority, but I was immediately put off when I saw "AI-native" on that page.

I don't want my incident management system to be AI anything. But then I thought maybe I'm being unreasonable so I checked out https://betterstack.com/docs/uptime/incident-silencing/ which was the first thing I found that was AI related.

Frankly, the thought of some black box AI system deciding when to silence incidents utterly terrifies me. I want to be absolutely 100% certain that I'm receiving all my alerts. If they're too noisy or repetitive, it's on me and my team to improve the alert quality, not leave it to "AI" to figure out what to silence.

[jurajmasar]

Thanks for the feedback!

The phrase "AI-native" increases your startup's valuation by 100x nowadays

(just kidding)

[MarekDlugos]

This is cool. Happy Better Stack customer here.