Simply check it out yourself at https://playground.keephq.dev or just have a look at our repo https://github.com/keephq/keep
We always had trouble with anything monitoring, observability and alerting, with and without OpenTelemtry. While trying almost every tool out there, we always lacked something and eventually found ourselves building complementary tools that fit our needs.
Keep is like a swiss army knife for alerts - anything from collecting, enriching, correlating, and automating. We have over 90 integrations: anything from alerts, topology (CMDB), ticketing, databases, etc., a GitHub-Action-like interface for your monitoring stack (we did a Show HN for it here: https://news.ycombinator.com/item?id=37381268) triggers manually, cron, alert or incident-based, a smart correlation layer, where we use LLMs or pre-configured rules to correlate alerts into incidents (imagine “DB is down” and plenty of 5XX from other services), opinionated or customized deduplication rules to view only the alerts that matter, extraction and mapping capabilities to extract/add missing bits of information to alerts, a single pane of glass to see and manage everything in one place and batteries-included LLM: chat with your observability data
Tools like BigPanda, Moogsoft, Splunk ITSI, or Datadog Event Management treat AIOps as a side quest – trying to vendor-lock or deploy AIOps for huge enterprises only while we build a tool that can serve organizations of any size.
We are completely open-source (MIT license), and we monetize on a SaaS-managed version and enterprise features: SSO, RBAC, Auditing, 24/7 support, longer retention, and private deployments.
We are excited to share what we’ve been working on for the last year and would love to hear your feedback and opinions!
Hosted Demo: https://playground.keephq.dev
Open Source: https://github.com/keephq/keep
Landing Page: https://keephq.dev
by Andrey
Azimov