Np! Company A have 4 monitoring tools and 2 IRM’s. Few dozens of alerts per day. They use Keep to streamline their ticketing routing, enriching the ticket from a prod db, some if/else logic. Every month they do some research on the alerts they had last month with slice and dice per team/app/etc.
Company B, with big operations group, use Keep as single pane of glass where NOC dispatch incidents and sync context from every system.
With slack you lose history and context. Also collaboration is harder. Also if you have some processes/workflows you want to maintain in some GitHub repo and manage as code/gitops, you can’t do it with Slack. Deduplicating alerts is also a thing. Basically it’s a different use case
for small teams we mostly see workflow automation on their alerts, for bigger teams it’s also unified API for alerts from many tools and single pane of glass for alerts
Yo! I can say that most of our users are open source users. We are community-driven, and like 95% of the features are open source. It’s true that we need something to monetize on but I really feel that we are an open source company.
valid feedback. If a company works only with Datadog it probably doesn't need a unified API for alerts, but what we see is that many companies use more than one. monitoring tool (or even other tools that generates alerts but arent classic monitoring tool)