We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
healthz
(Discussed on the dev-team meeting on Dec 15)
In the #881 we introduce a dedicated Botkube heatlhz endpoint that returns 200 (OK).
heatlhz
As a part of this task, we should return JSON with information about Botkube core health:
and enabled plugins (after Watch and respawn started plugins that exited #878)
and communications platform statuses (if possible)
Ensure the bot + plugin statuses can be used as a part of reportDeploymentHeartbeat GraphQL query
reportDeploymentHeartbeat
Provide visibility about Botkube and related components' health.
The text was updated successfully, but these errors were encountered:
madebyrogal
No branches or pull requests
Overview
(Discussed on the dev-team meeting on Dec 15)
In the #881 we introduce a dedicated Botkube
heatlhz
endpoint that returns 200 (OK).As a part of this task, we should return JSON with information about Botkube core health:
and enabled plugins (after Watch and respawn started plugins that exited #878)
and communications platform statuses (if possible)
Ensure the bot + plugin statuses can be used as a part of
reportDeploymentHeartbeat
GraphQL queryReason
Provide visibility about Botkube and related components' health.
The text was updated successfully, but these errors were encountered: