YDK library | Catching returned RPC from devices

[rcicu]

Hi there,

Is there any way if catching the returned RPC sting from the device, beside logging? 

I am asking this because I got a different vendor which is returning the XML indicating an error, but the return status is OK, so there is no way of raising that error to my app. The only way that I've identified until now is to capture the logs in a file and check the content of that one for my specific errors, but I don't like this approach

Cheers!

[ygorelik]

The RPCs are visible only in the logs with the log level INFO or DEBUG.

The YDK is open source software. So, you always have an option to make any changes in the code to your convenience.

Yan 

[rcicu]

Thanks for your replay!

Can you point me to the place where the action is take place? For example, in the lock method, I would like to check the messages exchanged under the hood on this object: 

return self._ns.lock(provider, target)

Thanks!

[yangorelik]

All the actions are happening in the C++ code (libydk library). The Python code is just a wrapper for C++ functions. Here is the link to the GitHub repository where NetconfService::lock() is implemented.