Skip to content

Commit

Permalink
Competition refined
Browse files Browse the repository at this point in the history
  • Loading branch information
@Matvey-Kuk
Matvey-Kuk committed Jun 16, 2024
1 parent 638817b commit e0cb561
Show file tree
Hide file tree
Showing 6 changed files with 6,929 additions and 30 deletions.
3 changes: 3 additions & 0 deletions .gitignore
View file
Original file line number Diff line number Diff line change
Expand Up @@ -191,3 +191,6 @@ storage

# otel files
tempo-data/

# docs
docs/node_modules/
9 changes: 9 additions & 0 deletions docs/README.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
How to run docs locally:

```
npm i -g mintlify
mintlify dev
```

Read more: https://mintlify.com/docs/development
54 changes: 26 additions & 28 deletions docs/overview/comparison.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,38 +4,36 @@ title: "Comparison"

Sometimes, it's easier to understand a tool's capabilities by comparing it to other tools in the same ecosystem. In this section, we'll discuss how Keep interacts with and compares to other tools in the ecosystem.

## Keep vs Alerta
## Keep vs AIOps inside observability platforms (Splunk ITSI, Elastic AIOps, etc)

> alerta monitoring system is a tool used to consolidate and de-duplicate alerts from multiple sources for quick ‘at-a-glance’ visualisation. With just one system you can monitor alerts from many other monitoring tools on a single screen
> [(alerta docs)](https://docs.alerta.io/).
Keep differs because it's able to correlate alerts between different observability platforms.

| | Keep | Alternative |
| --------------------------- | -------------------------------------------------------------- | ------------- |
| Aggregation and correlation | ✅ | ✅ |
| Integrations | ✅ (Both manually and automatically with Webhooks Integration) | ✅ (Manually) |
| Alerts enrichment | ✅ | ❌ |
| Open source | ✅ | ✅ |
| Workflow automation | ✅ | ❌ |
| Managed version | ✅ | ❌ |
| CI/CD integration | ✅ | ❌ |
| Noise reduction | ✅ | ❌ |
| | Keep | Alternative |
| ------------------------------------- | -------------------------------------------------------------- | ---------------------------- |
| Aggregation of alerts from one plaftorm | ✅ | ✅ |
| .. from multiple platforms | ✅ | ❌ |
| Correlation of alerts between multiple sources | ✅ | ❌ |
| Alerts enrichment | ✅ | ❌ |
| Open source | ✅ | ❌ |
| Workflow automation | ✅ | ❌ |

## Keep vs Grafana
## Keep vs dedicated AIOps solution (BigPanda, MoogSoft, etc)

> Using Grafana Alerting, you create queries and expressions from multiple data sources — no matter where your data is stored — giving you the flexibility to combine your data and alert on your metrics and logs in new and unique ways. You can then create, manage, and take action on your alerts from a single, consolidated view, and improve your team’s ability to identify and resolve issues quickly.
> [(Grafana docs)](https://grafana.com/docs/grafana/latest/alerting/).
BigPanda and Moogsoft are our direct competitors. Keep differs because it's open source which makes integration, and piloting easy. Our customer also noticed a significant difference in the alert correlation approach since we at Keep focus less on manual configuration and more on applying state-of-the-art AI models meaning it's easier for Keep to correlate alerts which never happened before.

| | Keep | Alternative |
| ------------------------------------- | -------------------------------------------------------------- | ---------------------------- |
| Aggregation and correlation of alerts | ✅ | ❌ |
| Integrations | ✅ (Both manually and automatically with Webhooks Integration) | ✅ (Manually) |
| Alerts enrichment | ✅ | ❌ |
| Open source | ✅ | ✅ |
| Workflow automation | ✅ | ❌ |
| Managed version | ✅ | ✅ |
| CI/CD integration | ✅ | ⚠️ has terraform integration |
| Noise reduction | ✅ | ❌ |

## Keep vs incident management tools (PagerDuty, OpsGenie, etc)

Most incident management tools offer features like alert aggregation and workflow automation. However, their core value is the incident management itself, which Keep aims to prevent. Keep focuses only on the alert lifecycle.
| Aggregation of alerts | ✅ | ✅ |
| Integrations | ✅ (Bi-directional) | ✅ (Webhooks) |
| Alerts enrichment | ✅ | ✅ |
| Open source | ✅ | ❌ |
| Workflow automation | ✅ (GitHub Actions-like, infrastructure as code) | ✅ |
| Managed version | ✅ | ✅ |
| On-Premises | ✅ | ❌ |
| Noise reduction & correlation | ✅ (AI) | ✅ (Rule-based in some cases) |

## Keep vs IRM (PagerDuty, OpsGenie, etc)

Incident management tools aim to "notify the right person at the right time," facilitate reporting, and create effective war rooms.

Keep focuses on the alert lifecycle, noise reduction, and AI-driven alert-incident correlation. Essentially, Keep serves as an 'intelligent layer before the IRM,' handling millions of alerts before they got fed into your IRM tool. Keep provides high-quality integrations with PagerDuty, OpsGenie, Grafana OnCall and others.
4 changes: 3 additions & 1 deletion docs/overview/introduction.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,10 @@ Alerts usually categorized into three different groups:
Keep helps with every step of the alert lifecycle:
1. Creation - Keep offers a framework for creating, debugging, and testing alerts through code that scales with your teams.
2. Maintenance - Keep integrates with your tools, allowing you to manage all of your alerts within a single interface.
3. Noise reduction - By integrating with monitoring tools, Keep can deduplicate and correlate alerts to reduce noise in your organization.
3. Noise reduction - By integrating with monitoring tools, Keep can deduplicate and correlate alerts to reduce noise in your organization. Rule-based (all distributions), and AI-based (Keep Enterprise only).
4. Automation - [Keep Workflows](/workflows) enable automated alert enrichment and response.
5. Incident Correlation - Automatically assign alerts to incidents (Keep Enterprise only).
6. Summorization - Summary of an incident based on past incidents and the knowledge base (Keep Enterprise only).

## How does Keep integrate with the alerts?
Alerts can either be [pulled](/platform/alerts#pulled-alerts) by Keep or [pushed](/platform/alerts#pushed-alerts) into it. Keep also offers zero-click alert instrumentation through [webhook installation](/platform/providers#webhook-integration).
Loading

0 comments on commit e0cb561

Please sign in to comment.