Skip to content

Better health check - ensuring propery connection to Kafka #86

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

Merged
merged 1 commit into from
Oct 8, 2024
Merged

Conversation

jmgasper
Copy link
Contributor

@jmgasper jmgasper commented Oct 7, 2024

Help to identify issues if the Kafka connection drops, like what we saw in prod recently. This should ensure that the ECS container is restarted if the Kafka connection fails.

@jmgasper jmgasper requested a review from testflyjets October 7, 2024 03:20
res.json({ health: 'ok' })
}
catch(err){
res.sendStatus(500);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to include the err in the response?

@jmgasper jmgasper merged commit 37b4371 into master Oct 8, 2024
3 of 4 checks passed
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

Successfully merging this pull request may close these issues.

2 participants