shahargl 6 hours ago

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

1
nextworddev 6 hours ago

ok but what problem does this solve that I can't solve with Slack notifs

shahargl 6 hours ago

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

nextworddev 5 hours ago

Thanks for the clarification. Would you be able to provide a concrete example for this product’s differentiated use case

shahargl 5 hours ago

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.

nextworddev 5 hours ago

Thanks. The first example painted a better picture