How can we improve error messages?

[HeyItsJs]

The problem faced currently

Right now there's now way to know the following:

• Whether SC has been successful to connecting to databases or not? If not why? (This been the major one)
• Whether SC is up and running properly
• version and environment SC is running in
• Is it running with SSL or not?
• Has it received new configurations from mission control?

Also on the client side after triggering a Space API, there is no way to figure out why a request was not successful. A few errors which should be easy to debug and logged in a better way are:

• Wrong project id
• Disabled module
• Database not connected
• Security rules failed

How can we solve it?

SC should be logging what id does at each stage during the init For example:

Space Cloud is a web server with a realtime data access layer and a powerful function mesh

Starting SC in dev mode with 0 projects..
Connecting to databases...
Connected to MongoDB successfully ✔
Could not connect to MySQL ✗
Downloading Mission Control UI....
Extracting Mission Control...
Done

Exposed HTTP APIs on port 4122
Exposed gRPC APIs on port 4124 

Open http://localhost:41222/mission-control to cofigure Space Cloud

Applying new config from Mission control...
Could not connect to MongoDB ✗
Make sure your MongoDB is up and running and its connection string is correct

On the client side, the errors should be more explicit and informative like:

• Bad request: The requested project-id does not exists. Make sure your project-id is correct and you are querying the right space-cloud
• Operation not supported: The database module is disabled
• Operation failed: Could not connect to database. Make sure your database is up and running

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features are important to you. 👍

[YourTechBud]

We can send status in the following format for gRPC: https://github.com/googleapis/googleapis/blob/master/google/rpc/status.proto