How to use error logs (Assistant for Developers Pro Tips)

[Music] if your action behaves oddly during development or your users report issues engaging with your action you're going to need to do some debugging but where to start in today's a og pro tips we'll explore how to use stack driver error logs to debug and improve the quality of your actions you can access the logs for your action by opening up the Google Cloud console make sure to select the ID of your project and select the logs option under stackdriver depending on how long your action has been running you may have hundreds or even thousands of login trays to review you can narrow down your search by filtering by the logs urgency level date and time resource type or underlying API to quickly narrow the list entries related to your actions functionality select google assistant action under resource type once you've found the log entry you need you can expand it to find more details about exactly what failed the text payload includes information like the request ID conversation ID and invocation use for the action helping you quickly identify what intends to debug sometimes looking at a single log entry by itself won't give you enough information about the issue to see where the error fell in relation to other events in the fulfillment flow you can select show in resource context and view all logs from the same date and time to help with the development workflow collaborators who have admin access to your action can automatically access the error logs in stackdriver additionally if you identify repeated problematic behavior of your action you can deploy filters to isolate the applicable log entries and automatically export those logs to your own server this allows you to be notified promptly of continuing issues and to share insights with your development team easily for more pro tips be sure to check out the rest of the videos and share your thoughts with us on twitter using the hash tag aog pro tips thanks for watching