Skip to content

Conversation

@JibinKoshy07
Copy link

Added a health check for taiga-events-rabbitmq since taiga-events was exiting during initial startup due to its dependency on taiga-events-rabbitmq.

@b2cc
Copy link

b2cc commented Nov 6, 2025

Maybe check_local_alarms would be more useful? It could catch conditions where e.g. RabbitMQ is running into low memory watermark and basically stops working, yet it would still report ok during check_running. And it would also fulfill your requirement as it only reports ok when RabbitMQ is actually running.

@JibinKoshy07
Copy link
Author

@b2cc You're absolutely right — using check_local_alarms would provide a more reliable health indicator, especially in cases where RabbitMQ is running but has hit memory or resource limits. It indeed makes more sense since it only reports OK when RabbitMQ is actually healthy and running properly.

@b2cc
Copy link

b2cc commented Nov 6, 2025

@JibinKoshy07 : maybe we should merge our two PRs into one (I submitted #153)

If it's ok for you I'd put together a new PR with your changes as well, and we can close the others.

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