When a weather request made by the previewer onto the broker fails we get systematically three logs:
- HTTP status code
- HTTP status message
- a more functional logs with a detail
See below:
2021-01-13 18:07:10,257 ERROR [RenditionWeatherPolling] [com.arondor.arender.viewer.common.rest.BaseRestClient] Response [503] for weather 2021-01-13 18:07:10,257 ERROR [RenditionWeatherPolling] [com.arondor.arender.viewer.common.rest.BaseRestClient] Non-successfull status : Service Unavailable 2021-01-13 18:07:10,258 ERROR [RenditionWeatherPolling] [com.arondor.viewer.common.rendition.connector.RemoteClientServiceInvoker] Could not fetch performance score for address=http://arender-pool-green-document-service-broker.int-arender-preprod.svc:8761/ , exception=Error reading entity from input stream.
Getting this information on the previewer is interesting and can be a log to follow to detect NEV errors.
Nevertheless, logging three times the same error with different information can be problematic. Logs could be interlaced with other errors, making the diagnostic more complicated.
Request
- The three logs should be merged into a single one.
- The exception message on the third one is not always intuitive, on the example above, 503 == error reading entity from input stream, shouldn't be a connection timeout or something equivalent?