shahargl

As the one who wrote it, I thought about using "we" vs "I" (and in other places I did use "I"), but its bit overthinking about what I tried to say. But anyway will be take more caution next time

Hey! I’m the one who wrote it. Saw you asked for a non-x link -https://shahar.blog/2026/11/08/on-being-an-engineer-in-2026/

I need to update my profile, I’m Tech Lead at Elastic after we got acquired

what avoids me to create "while true requests.get()" to get as many as pixels as I want?

thanks! <3

Thanks! what would you expect from dark mode?

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.

Interesting! What type of integration do you imagine?

How does it play with Keycloak's Authorization Services?

Or in other words - why should I choose permify over Keycloak? https://www.keycloak.org/docs/latest/authorization_services/...

https://github.com/keephq/keep (disclaimer - i'm the maintainer)

how is it different from Traceloop and openllmetry (https://github.com/traceloop/openllmetry)?

one of the concepts we are trying to push is exactly that - my cofounder actually wrote a blog post about it - https://news.ycombinator.com/item?id=38086082

So the goal is to have unified interface for every tool you’ve just mentioned

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)

the roadmap is available at https://github.com/keephq/keep/issues feel free to create ticket if anything missing

100%

Yet again, that’s about the data, I think the blog post focuses on the applicative aspect

But that’s for the data part (otel) and not the applicative part (alerts, dashboards, etc)

Cool! Never heard of it and definitely gonna check it.

Wdym by moving people?

You should read this to get the full context - https://news.ycombinator.com/item?id=34540419

Nope, fully open source - https://github.com/keephq/keep

hey there! we had the exact same problem so we built https://github.com/keephq/keep. it's cool to see that we have very similar syntax (you can see workflows examples here - https://github.com/keephq/keep/tree/main/examples/workflows)

Yea I was wondering specifically on those (although any other context is welcome)

hey! would be cool to chat about what you've build. we are currently building Keep (https://github.com/keephq/keep) where you can define alerts as YAML's. would be cool to learn from you.

Hey! I've missed your reply here. Sent an email.