Simple Alerting CLI tool, built-in providers (e.g., sentry/datadog or slack/pagerduty), easy-to-learn YAML workflows (GitHub Actions-like syntax), freedom from vendor lock-in, 100% open sourced, free forever.
Alerting, by developers, for developers
Simple Alerting CLI tool, built-in providers (e.g., sentry/datadog or slack/pagerduty), easy-to-learn YAML workflows (GitHub Actions-like syntax), freedom from vendor lock-in, 100% open sourced, free forever.
Hi Product Hunters 👋! Thrilled to announce that we're open-sourcing our alerting CLI tool, Keep ( https://github.com/keephq/keep ) 🗼. Designed by developers for developers, Keep streamlines and simplifies alerting, making it a first-class citizen within the development process. Think of Keep as Prometheus Alertmanager but for all observability tools, with a simple and intuitive (GitHub actions-like) syntax. We believe that alerting has historically been neglected in existing monitoring platforms
Love it! Alerting: the bane of dev’s existence. What does a slack integration look like? (Can I customize it?)
Tested it and works great. Will defo integrate into our stack soon
Awesome! Will the scoring system also be part of the free open source?
Alert fatigue is TOO real! But getting too fancy with selective monitoring can be catastrophic - how do you guys make sure the mission critical stuff doesn't get dropped on the floor with the scoring system?
A measure of community engagement at launch. Higher means more people noticed and interacted with the product. It's a traction signal, not a quality rating.
Discussion threads divided by interest score. Above 0.30 is strong. Below 0.15 suggests the product got clicks but not conversation.
Categories come from the product's launch tags. Most products appear in 2-3 categories. The primary category is listed first.
The scores reflect launch-period engagement. Historical data is preserved and doesn't change retroactively. The build date at the bottom shows when the index was last refreshed.