[HN Gopher] Launch HN: Keep (YC W23) - AIOps and alert management
       ___________________________________________________________________
        
       Launch HN: Keep (YC W23) - AIOps and alert management
        
       Hey HN, Matvey, Shahar, and Tal from Keep (keephq.dev) here. Keep
       lets you easily centralize alerts from any monitoring tool and
       correlate (manually or AI-based), enrich, deduplicate, filter, and
       then run automation (such as auto-recovering or ticketing sync).
       For example, if you have Sentry for your exceptions, Prometheus for
       metrics, and your cloud provider for logs, you can easily send all
       the alerts to Keep and get a great interface to run workflows.
       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
        
       Author : talboren
       Score  : 69 points
       Date   : 2024-11-27 15:58 UTC (7 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | sidcool wrote:
       | Congrats on launching.
        
       | nadavwiz wrote:
       | Looks great! What about some Zapier support?
        
       | eylonmiz wrote:
       | Congratz on the launch! is it relevant for early-stage products
       | with small teams or is it an overkill? we're just kicking our
       | observability tools (Vercel, AWS - ECS infra)
        
         | talboren wrote:
         | it's definitely relevant for early-stage products who deeply
         | care about realiability. are you already handling some amount
         | of alerts today? there's a bunch of stuff you can do with
         | workflows to automate processes and help your users.
         | 
         | we do integrate with AWS Cloudwatch but not yet with Vercel's
         | observability, but can add that if you want to give it try
        
           | eylonmiz wrote:
           | We will check the Cloudwatch integration, thanks!
        
       | cdchn wrote:
       | Small typo on your "Mapping" page "Enirch alerts with more data
       | from Topology, CSV, JSON and YAMLs"
        
         | talboren wrote:
         | thank you for that! fixed in
         | https://github.com/keephq/keep/issues/2681
        
           | benatkin wrote:
           | I love me some worfklows. Please keep this typo...pretty
           | please? :)
        
             | talboren wrote:
             | haha! gotta fix those for my ocd:
             | https://github.com/keephq/keep/pull/2684 ^^'
        
               | benatkin wrote:
               | At least it will be preserved in the PR title.
        
           | ShayNehmad wrote:
           | Damn, answering feedback with a pr link is fireeee
        
             | talboren wrote:
             | trying to keep that high pace!
        
       | sofixa wrote:
       | Contrats on the launch, this looks pretty good, interesting,
       | useful, and especially for such a stage, integrated with a ton of
       | things!
       | 
       | If you're taking feature requests, it would be pretty cool if you
       | added support for Nomad[1] as an orchestrator too.
       | 
       | 1 - https://nomadproject.io/
        
         | shahargl wrote:
         | Interesting! What type of integration do you imagine?
        
         | motakuk wrote:
         | Deployment with Nomad should be pretty straightforward
         | following https://github.com/keephq/keep/blob/main/docker-
         | compose.yml or https://github.com/keephq/helm-charts
        
       | zlatan_todoric wrote:
       | It looks quite interesting, that's said, I wish people would stop
       | calling projects open source when they aren't and most if not all
       | projects here in Show/Launch are open core - same with Keep. You
       | have a proprietary license in the project, with parts of the code
       | with an open source license.
        
         | shahargl wrote:
         | 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.
        
         | motakuk wrote:
         | Companies adopt different strategies when building Open Core
         | products. Some aim to keep the Open Source portion minimal,
         | reserving the most valuable features for their paid versions.
         | At Keep, we chose the opposite path--moving nearly everything
         | into Open Source. Our philosophy is that most users should be
         | able to fully benefit from the Open Source version.
         | 
         | While I understand (and share) the caution around licenses, I
         | don't think this concern applies to Keep. With 99% of our
         | codebase under the MIT license, it's a far cry from just having
         | "parts of the code with an open source license."
         | 
         | I recommend running Keep locally and comparing the Open Source
         | version to the playground where full version is running. You
         | might find it challenging to spot the differences.
         | 
         | I also reccomend comparing Keep Open Source to BigPanda and
         | Moogsoft. It may be surprising how much of it Keep OSS, real
         | MIT-licensed Keep has.
        
         | dang wrote:
         | Ok, I've taken "open source" out of the title now. The
         | definitional argument here isn't really on topic.
        
       | bzmrgonz wrote:
       | $1/alert/month???
        
         | talboren wrote:
         | actually, it's 100 workflows, 20 providers and 10 users.
         | important to note that it's per deduplicated alert and not
         | every event ingested by keep. what got you surprised about this
         | pricing model?
        
       | pranay01 wrote:
       | Congrats on the launch!
       | 
       | TIL that BigPanda and Moogsoft solve the same problems which you
       | are trying to solve :)
       | 
       | Would have loved to see SigNoz also in the list of supported
       | integrations
        
         | talboren wrote:
         | providers are usually driven by the community! happy to
         | collaborate on that provider if you'd like.
        
       ___________________________________________________________________
       (page generated 2024-11-27 23:00 UTC)