Improve logging output format based on actual binding of Application Logging service or some env property

From the documentation:

If VCAP_SERVICE variables are present in the environment variables the kibana format is used, because the SAP Cloud SDK assumes your application is running on Cloud Foundry.

It appears to do just that, only having any VCAP_SERVICE in the environment variables is too broad. When developing locally, most of the time there will be some VCAP_SERVICE set, not because it’s running in CF, but because they are being set through default-env.json or otherwise to hook into CF services from the local runtime.

This means at the moment Cloud SDK is very often wrongfully assuming it’s running in CF, when it’s not.

Proposal: check for both the presence of the Application Logging service in VCAP_SERVICE or the explicit configuration of requesting Kibana specific formatting output through the presence of an environment variable. For example features.kibana_formatter=true which is also used for CAP.

[marikaner]

Seems that we lost track of this. I now prioritized it higher in our backlog. No promises when this can be done, but it’s back on our plate.

[jjtang1985]

Hi @piejanssens ,

We implemented the feature about a month ago and the stable version was released. Please try version 2.5.0. Here you can find the updated doc regarding the log format.

Please reopen, if you have questions.

Best, Junjie