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

Health of API and debug API should be websocket connection #17

Open
vojtechsimetka opened this issue Mar 10, 2021 · 4 comments
Open

Health of API and debug API should be websocket connection #17

vojtechsimetka opened this issue Mar 10, 2021 · 4 comments
Labels
status:blocked Unable to be worked further until needs are met (see 'need:*' category) type:issue

Comments

@vojtechsimetka
Copy link
Contributor

Both standard API and debug API should have health endpoint which would be websocket. This way the bee-status can monitor the endpoint and alert user if anything goes wrong.

@vojtechsimetka vojtechsimetka added the status:blocked Unable to be worked further until needs are met (see 'need:*' category) label Mar 10, 2021
@agazso
Copy link
Member

agazso commented Mar 11, 2021

These would require changes from the Bee side too. We can have this functionality by setting up a timer that checks the health endpoints without websocket.

@vojtechsimetka
Copy link
Contributor Author

Yes that is the ultimate idea - to have a discussion about such endpoint on Bee.

Great suggestion with the polling solution.

@acud
Copy link
Member

acud commented Mar 16, 2021

On bee side - not sure, since k8s is polling these endpoints too, it means that they might need to be implemented to support both ws and normal json responses. Which is probably doable. Not sure how urgent this is though.

@Eknir
Copy link

Eknir commented Mar 18, 2021

@vojtechsimetka , if this functionality can be implemented also on the js-side, I would suggest to do it like that for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:blocked Unable to be worked further until needs are met (see 'need:*' category) type:issue
Projects
None yet
Development

No branches or pull requests

4 participants