Visualize the reasoning why a Service Ping failed
Summary
Add a way to visualize the errors we collect from self-managed instances when a Service Ping fails
Errors are collect with the changes introduced here !78028 (diffs)
Why?
This could help us understand the reason of a failure and give us information on how can be fixed
Details
With !78028 (diffs) we added a POST request that returns a JSON in case of exception.
When we release the 14.8 version we will start receiving these logs
Logs format(This was from a test)
Feb 17 15:20:06.343 | production-5576b8b87-h7d5c | I, [2022-02-17T13:20:06.343318 #84] INFO -- : [55ccaf4cfde827f882f4227517a33fef] Parameters: {"error"=>{"time"=>"2022-02-17T13:20:05.712Z", "uuid"=>"02333324-1cd7-4c3b-a45b-a4993f05fb1d", "hostname"=>"127.0.0.1", "version"=>"14.8.0-pre", "message"=>"Error to be logged 1", "elapsed"=>20.1}, "usage_ping_error"=>{"error"=>{"time"=>"2022-02-17T13:20:05.712Z", "uuid"=>"02333324-1cd7-4c3b-a45b-a4993f05fb1d", "hostname"=>"127.0.0.1", "version"=>"14.8.0-pre", "message"=>"Error to be logged 1", "elapsed"=>20.1}}}
Testing
Update unit tests and make sure QA pipelines are passing with these changes
Edited by Carlo Catimbang