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

Heartbeat response #1388

Closed
prasm313 opened this issue Feb 2, 2024 · 2 comments
Closed

Heartbeat response #1388

prasm313 opened this issue Feb 2, 2024 · 2 comments
Labels
backend Backend related functionality feature New feature or request

Comments

@prasm313
Copy link
Contributor

prasm313 commented Feb 2, 2024

Describe the improvement you would like to see
Ref meeting 31.01.24:
Implement a way for Isar to know if the backend is down. Isar may use this information to stop the robot if the heartbeat disappears.

Describe the solution you'd like
In addition to the MQTT heartbeat from Isar to Flotilla, a heartbeat signal over the API should go from Flotilla to Isar.

How will this feature affect the current Threat Model?
N/A

@prasm313 prasm313 added backend Backend related functionality breaking-change A breaking change which introduces changes to the public APIs feature New feature or request and removed breaking-change A breaking change which introduces changes to the public APIs labels Feb 2, 2024
@aeshub
Copy link
Contributor

aeshub commented May 3, 2024

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label May 3, 2024
@Christdej Christdej removed the stale This issue or pull request already exists label Aug 5, 2024
@Christdej
Copy link
Contributor

Probably not needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend related functionality feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants