Provide more detailed error logging
Error message logs sometimes are not detailed enough to properly troubleshoot. The customer would like to increase logging available in order to get more insight as to what is going on.
One example - the PI Integrator for BA does not publish any message when there is a permissions/access issue to output data to a Kafka Topic.
Carol Pontes Pontes Lara commented
Agree. PI Vision has got a generic "Internal Server Error" which is not detailed enough to troubleshoot. In most of the situations, where "Internal Server Error" occurs, the message logs do not lead to the root cause of the issue and we can not make improvements towards resolving those problems.
If we can have more granular message logs popping up, that would help guiding improvements in the system.
Guy Acciai commented
Very much agree - and this can be in the Target setup stage, I'm fighting a similar issue with AWS Kensis - Basically just getting a "failed to connect to stream" message, versus details about what calls where attempted in the AWS SDK, and more importantly, any return status/error codes.