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

[BUG] Monitoring and status routes don't monitor services #1624

Closed
davidvitora opened this issue Mar 23, 2022 · 1 comment · Fixed by botpress/botpress#11716 or botpress/botpress#11769
Labels
bug Something isn't working

Comments

@davidvitora
Copy link
Contributor

Describe the bug
Monitoring routes that are used to determine how healthy the bot is are not taking the different services to check if the bot is healthy or not.

To Reproduce
Steps to reproduce the behavior:

  1. Start a standalone messaging server and a Botpress instance connecting to it.
    image
  2. Stop the messaging server
    image
  3. Note that if try using the web-channel it will not work, but it will be marked as healthy at the monitoring route.
    image
    image
  4. At the status route it is also marked as up
    image

Expected behavior
To the health and status routes to mention some issues with the server

Environment (please complete the following information):

  • OS: Docker
  • Botpress Version 12.26.12
@github-actions
Copy link

github-actions bot commented Apr 26, 2022

Available on v12.27.0

@michaelmass michaelmass transferred this issue from botpress/botpress Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant