At SAP, we were analyzing the problems which our customers have when creating Syslog drains and the whole user experience when creating and configuring Syslog drains.

We have noticed the following:

• The Syslog Drains are created with as user provided service and there is no validation on creation time about connectivity and proper configuration in case if mTLS is configured;
• Only the foundation operators are informed about the problems with Sylsog drains

We should add application related logs in the app log stream where ever it is possible, so that the app devs are also informed about problems with their syslog drains.

I've checked the code and we the app_guid in the binding poller. We could propagate the app_guid and add a go-loggregator client with which we will emit the logs in the app's log stream. There is already something coded in the emitLoggregatorErrorLog in the Syslog Connector.

We will provide a PR about this.