Within your own driver, mostly--this is what try and catch are for. However, that only applies if the error was generated by code you wrote (or are calling in that code and isn't handled elsewhere). There are some things you won't be able to see this way (e.g., if you didn't imement a command for a capability and the platform tries to call the corresponding method), and it's not related to Logs per se; the connection is that unhandled exceptions in your code are automatically pushed to Logs, and this is one way to handle them yourself.
This won't help you with other devices or apps, only the device or app code you're writing. There is no official way to do that, though some have unofficially managed to scrape the (I think?) websocket live logs are sent through.
Not sure which of these is more of what you mean, but hopefully that helps a bit.
