server: enabled option for default health check service for mavsdk grpc server. #1799
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enables the default grpc health check service for the mavsdk_server. Such a service is useful to check if mavsdk_server has started serving before clients would try to connect it. Documentation on this service is at gRPC-C++ Health Check Protocol
Once enabled, a CLI client like grpc_health_probe can be used to check if the service is serving or not.
Example 1: MAVSDK Server is not yet connected to any autopilot so not listening on port 50051.
Example 2: MAVSDK Server IS conencted to a autopilot and listening on port 50051