Keep

We have a new member who is joining the Keep fam! Welcome Ihor Panasiuk Ihor is a skilled full-stack developer with extensive experience in both front-end and back-end development, adept at crafting seamless and efficient web applications. Beyond coding, likes building radio-controlled airplanes of different materials. 📡🛩️ We are excited to have you onboard and look forward to what we will build together! 🚨

Hey folks! 👋 I’m Vladimir, a Founding Engineer at Keep, and I’m fulfilling my end of a friendly wager gone wrong. 😬 Recently, I bet the team on how many GitHub stars our open-source product would gain by the end of our latest spike. Spoiler: I underestimated the power of our social efforts and, well… here I am! 😅 Join me for 2 hours of test writing for our open-source project, as I work on improving code quality, adding some coverage, and probably sharing a few laughs along the way. If you’re curious about testing, open-source contributions, or just want to see how I recover from losing a bet, come hang out! 🙌 When: Dec 17, 13:00 UTC Where: https://lnkd.in/d-G2DNDF Let’s write some tests, and maybe I’ll even win the next bet! 🚀

Providers are what we call integrations in Keep. They are bi-directional, allowing us to receive and query data from the 3rd party tool but also to push data to it. The team at Keep created a new metric we call "MTTP" (the joke is on us 😅), which stands for "Mean time to Provider" - it's how we measure how fast we can deliver new requirements whenever a request from the community arises. This issue, for example, https://lnkd.in/dJsXeZCX, about adding AdaptiveCards support for our Teams Provider, took < 24 hours to complete. This is how quickly we move. That's the pace! ⚡️ We aim to keep this metric below 48 hours. You ask for a new integration? We get it done. Fast. Go team Keep

In rare cases where he's not working on making our UI incredible, he's creating incredible memes; nice one Kirill! 👏😍

When you think Saturday will go easy and then: Keep #oss

We are trending 🧨 https://lnkd.in/dpNZ66-w

Keep is trending on GitHub. I love being OpenSource 🤩

🚨 We launched Keep on Hackernews (https://lnkd.in/ez3tmEa) and built a playground that demonstrates the power and value you can get from Keep with data in place and integrations connected. Keep is a swiss army knife for alerts - anything from collecting, enriching, correlating, and automating. - More than 90 integrations: anything from alerts, topology (CMDB), ticketing, databases, etc. - a GitHub-Action-like interface for your monitoring stack that 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 that relate with each other). - 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 - batteries-included LLM: chat with your observability data Wanna know more? Check out https://lnkd.in/eumFa4Du and share your feedback with us! ✨

Let’s talk about the importance of the service map in root cause analysis. Imagine this scenario: you get an alert storm on your #alerts-prod channel with numerous 5XX errors on your API service, random error messages, and some alerts on your database. Alert fatigue. But what if you knew these alerts were dependent on each other, so the database is the root cause, and all the other alerts are side effects? Enter the service map. Identifying the dependencies between services can easily reduce MTTR and solve alert fatigue. Instead of looking at dozens of alerts, you focus on just one. Keep can automatically correlate alerts based on service map dependencies. You just connect your service map tool (e.g., Datadog, ServiceNow, or even Cilium), and your alerts get another layer of context for free.

Today, one of Keep's open-source community members shared an exciting screenshot with us. It was from a representative of a large bank (with over 15,000 employees) who has been evaluating Keep for the past month. They have successfully integrated four monitoring tools: Splunk, Zabbix, Graylog, Inc., and Checkmk. They loved how things were going and shared what's next on their list: setting up extraction rules, connecting their ticketing systems, and adding more monitoring tools. This is what makes open source so great - people just show up in our Slack, start asking questions, and get really into it. We love seeing folks embrace AIOps and join our community. And the bonus is that after a month of helping them out, they hit us with: "Going to show this to my manager and try to get a budget for a license."