Kener.ing is an open-source status page system that lets users track and display the status and incidents of various components or services.
Allows you to track and display ongoing incidents, providing detailed updates such as investigation, identification, monitoring, and resolution timelines.
Displays availability statistics for various components or services over a 90-day period, indicating their current status as up, degraded, or down.
Provides tools for monitoring application performance with real-time insights.
Offers capabilities to monitor network software in real-time for better visibility.
Allows posting HTTP endpoints or push data to monitor using REST APIs.
Handles different timezones automatically for visitors viewing the status page.
Supports cron-based scheduling for monitors with minimum per-minute intervals and can handle complex checks like polling, chains, secrets, etc.
Offers a pre-built Docker image for easy deployment and setup.
Enables customization of the status page along with badge generation and support for custom domains.
Allows embedding the monitor as an iframe or widget.
Includes support for multiple languages for a broader audience reach.
Ensures fully accessible design for all users, meeting high accessibility standards.
Responsive design optimized for various devices including mobile and desktop.
Automatically optimized for search engines and social media platforms.
Allows users to update the status of a monitor with attributes like status, latency, timestamp, and tag. It provides flexibility to set current operational status through simple API calls.
Enables users to get the current status of a specific monitor by tag. Users can easily see the latest status with a simple API request, which is handy for real-time monitoring purposes.
Provides APIs to manage and interact with incidents, supporting operations such as creating, updating, deleting incidents, and managing related data, which is crucial for maintaining a comprehensive incident management system.
Allows you to set environment variables necessary for running the application. It ensures proper configuration by copying from a sample file.
Guides the user through creating a new user for the application with a simple setup page, requiring name, email, and password.
Enables logging in using credentials provided during user setup.
Checks the status of a website or web app at different intervals. Can be configured for specific status codes or responses and use environment variables to add secrets.
Verifies the status of a DNS server at various intervals to ensure it is operating correctly.
Monitors the status of a server by checking its connectivity at different intervals.
Interpolates data for missing intervals by using previous data points. If no previous data point exists, it considers the status as up.
Sends emails when something goes wrong. Configurable to send to different addresses using a specified API key.
Sends messages to specified Slack channels when issues occur. Requires a Slack URL for configuration.
Sends messages to Discord channels when an issue arises. Requires a Discord URL for configuration.
Sends a message to specified webhooks when an issue is detected. Needs webhook URL; method will be POST.
Creates and manages incidents when something goes wrong, allowing tracking of incident status and updates.
Updates incidents using comments with status and timestamps, with the latest status being the current one.
Add monitors as affected components for an incident, affecting the incident's status based on severity.