Repository navigation
Welcome to Kener Feature Requests #119
Replies: 11 comments 16 replies
|
Add SMTP Fuctionality. I think its an non-brainer to add that. |
|
Add functionality to add "scheduled maintenance" windows that will happen in the future, show which service they affect and how log they are planed, as bonus could even add cron based repeating windows. |
|
Please add option to disable Google Fonts (that also removes the prefetch headers) or allow upload of fonts to serve then locally, there's some legal privacy issues with google fonts from their cdn. |
|
If I try to add a trigger type to the project, could you please confirm if the following steps are correct?
Is this sufficient? I apologize for my lack of experience with Node.js project development. |
|
I would like to have a rich-text editor in the incident summary and maintenance summary. |
|
Add functionality to process gRPC calls. |
|
I'd like to add a maintenance event via API. The current implementation of the incident API ignores the end date, state and status. curl 'http://localhost:3000/api/incident' \
--request POST \
--header 'Content-Type: application/json' \
--header 'Authorization: <redacted>' \
--data '{
"start_date_time": 1744717097,
"end_date_time": 1744724289,
"incident_type": "MAINTENANCE",
"title": "test api maintenance 1",
"state": "RESOLVED",
"status": "OPEN"
}'
{"id":6,"start_date_time":1744717097,"end_date_time":null,"created_at":"2025-04-15 12:33:26","updated_at":"2025-04-15 12:33:26","title":"test api maintenance 1","status":"OPEN","state":"INVESTIGATING"} |
|
|
Hello Thanks for your work, it's very nice and simple. I have 2 requests/ideas :
Thanks |
|
Problem Proposed Solution Kener stays in one central location and remains the single status page and source of configuration. A probe, ideally a small Docker image, runs at each remote site. It pulls its assigned monitors from the Kener server, runs the checks locally, and sends the results back. Each monitor can be assigned to a probe or location, and results are labeled with the location they came from. Probes connect outbound to Kener and authenticate with an API key, so no inbound firewall rules are needed at remote sites. If a probe stops reporting, its monitors show an unknown or degraded state rather than going stale silently. The probe API (fetching assigned monitors and submitting results) should be documented and versioned, so third-party probes can be built for environments where Docker isn’t an option, for example a native Windows service. Push monitors through the REST API can approximate this, but each site then needs custom scripts. Check definitions end up scattered across sites instead of being managed in Kener, and there’s no central view of probe health. Zabbix (proxies), Icinga and Nagios (satellites and agents), and many hosted uptime services support distributed checks from multiple locations. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:
build together 💪.
All reactions