Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client crashes when an alert with incident creation is raised #295

Open
antonio-sessa opened this issue Feb 18, 2025 · 0 comments
Open

Client crashes when an alert with incident creation is raised #295

antonio-sessa opened this issue Feb 18, 2025 · 0 comments

Comments

@antonio-sessa
Copy link

Describe the bug
Client crashes when an alert with incident creation is raised

Steps to reproduce

  1. I have installed kener locally on my Docker instance, reachable via http://localhost:3000/.
  2. I've correctly setup the Slack trigger, and when I test it I can get the notification on my Slack channel
  3. I've setup a monitor, with NONE as Monitor type
  4. I've setup an alarm trigger with Incident creation, when an alarm occurs.

I've tried to send an api request as
curl 'http://localhost:3000/api/status' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer <my-api-key>' \ --data '{ "status": "DOWN", "latency": 100, "tag": "my-degraded-website" }'
and the client stops, an in the logs I see (please see attachments)
Error: Undefined binding(s) detected when compiling FIRST. Undefined column(s): [id] query: select "id", "title", "start_date_time", "end_date_time", "created_at", "updated_at", "status", "state", "incident_type" from "incidents" where "id" = ? limit ?

Version
Latest stable release at 2025-02-18 (aka 3.1.5)

Environment
docker - version 27.4.0

Database
postgres - version 17.3

I've started kener for the first time directly on PostgreSQL instance, so no migration was needed

Screenshots
Image
Image

rajnandan1 added a commit that referenced this issue Feb 19, 2025
Improves incident display and management by introducing configurable incident group views and enhancing comment rendering to support HTML content.

Solves the bug raised in #295 where server crashes when an incident is created from an alert

Refines SMTP email settings by adding TLS configuration and allowing username/password to be optional. #300 and #298

Also, fixes a bug where only home page was being filtered. Now all pages are filtered. #297
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant