[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 : 91 points
Date : 2024-11-27 15:58 UTC (1 days 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?
| sofixa wrote:
| Similar to the other orchestrators, doing restarts and
| deployments and maybe even scale outs.
| 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.
| zlatan_todoric wrote:
| Kudos. I appreciate the desire to be open source and the need
| to monetize (and I don't have a golden solution to it, so I
| would probably do something similar), but I just wish that
| people clearly define that they are open core because there
| are a lot of amazing open source projects out there, and it
| wouldn't be fair to them to be called open source when they
| aren't.
| talboren wrote:
| thanks for the clarification, sorry if it sounded like
| we're thinking your comment is not legitimate. It
| absolutely makes sense.
| 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.
| zlatan_todoric wrote:
| Sorry, maybe I sounded diminishing in my post, and I didn't
| want that. However, the business is still open-core, even if
| 99% of it is open source. That 1% can taint the project more
| and more in the future (and MIT obviously allows for the
| open-source part to go fully proprietary in the future).
|
| 1% of cyanide compared to your body weight is still lethal.
|
| P.S. I played a bit last night and I will for sure give it a
| try (I'm an idealist but still pragmatic and I hope people at
| Keep are similar)
| motakuk wrote:
| Regarding the "1% of cyanide" comment, I'd like to share
| another perspective :)
|
| Almost every tech company has private code--typically
| stored in private repositories. When working on Keep, we
| faced a decision: should we place certain code in the EE
| folder under a different license or keep it in a private
| repo, only sharing it with a small group of enterprise
| customers who explicitly requested it?
|
| We chose to put that code on GitHub.
|
| Ironically, putting more code in the GitHub repo made it
| appear "less open source," even though we could have simply
| hidden it, making the repo look like "clean OSS" as
| multiple companies do. For example, those who put their
| products without Web UI to the open source, build UI
| privately and serve the "full" version in the cloud.
| zlatan_todoric wrote:
| Fair arguments and criticism. That doesn't make them
| better at all, I think we can agree on that (and as you
| mentioned the Web UI situation, yeah, that makes them way
| worse in gran total).
|
| I wish you all good luck, the product looks good, I hope
| you monetize it and I hope no big corp forks it and makes
| some closed source alternative (because MIT license does
| allow exactly that).
| 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?
| RadiozRadioz wrote:
| I work in e-commerce at a large marketplace.
|
| In surprised because 500 deduplicated alerts requiring human
| attention is a normal day for my company. If something goes
| really wrong it'd start to get very expensive.
| 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.
| nextworddev wrote:
| What's an actual use case for this?
| shahargl wrote:
| 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
| nextworddev wrote:
| ok but what problem does this solve that I can't solve with
| Slack notifs
| shahargl wrote:
| 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 wrote:
| Thanks for the clarification. Would you be able to
| provide a concrete example for this product's
| differentiated use case
| shahargl wrote:
| 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 wrote:
| Thanks. The first example painted a better picture
| mxcrbn wrote:
| product is slick, congrats on building this guys!
| shahargl wrote:
| thanks! <3
| rsp1984 wrote:
| Product looks solid but please stop it with that dark mode joke.
| I'm technical within all definitions you could possibly come up
| with but white-on-dark is just unbearable for my eyes.
| shahargl wrote:
| Thanks! what would you expect from dark mode?
| crazytweek wrote:
| There are a lot of studies that proof that darkmode during
| day is straining eyes much more. In the night dark mode is
| better. But most of the "day-to-day" user are working during
| day.
| talboren wrote:
| are you referring to the product or the toggle in our marketing
| website?
| animesh10k wrote:
| how big is this problem? do they recognise it first hand
___________________________________________________________________
(page generated 2024-11-28 23:02 UTC)