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.

Sign up for GitHub

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

Jump to bottom

feat: endpoint for uplink connection status #350

Merged
merged 2 commits into from
Jul 9, 2024
Merged

feat: endpoint for uplink connection status #350

merged 2 commits into from
Jul 9, 2024

Conversation

de-sh
Copy link
Contributor

@de-sh de-sh commented Jun 17, 2024 •
edited
Loading

Closes #

Changes

/status uplink console endpoint that returns a JSON text object: {"connected": true} or {"connected": false} depending on MQTT connectivity.

NOTE: Since timeout is by default 30 seconds, network connectivity will show up as online despite actually being down/half open.

Why?

Connected application might want to know if uplink is currently connected to the platform/broker

Trials Performed

$ curl -X GET http://localhost:3333/status
{"connected":false}⏎
$ curl -X GET http://localhost:3333/status
{"connected":true}⏎

@de-sh de-sh requested a review from shrbb June 17, 2024 18:01
@de-sh de-sh changed the title feat: endpoint for liveliness/network connection feat: endpoint for uplink connection status Jun 18, 2024
@de-sh de-sh merged commit 51f7745 into main Jul 9, 2024
2 checks passed
@de-sh de-sh deleted the liveliness branch July 9, 2024 11:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@shrbb shrbb Awaiting requested review from shrbb

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@de-sh