\n
![\"\"](\"https:\/\/i0.wp.com\/practicalpowershell.com\/wp-content\/uploads\/2021\/01\/PSTOTW-2021-01-25.jpg?ssl=1\")
<\/a>\nWe can see that all worked as expected and we are ready to go (prereq-wise). We also see that there is a Start and End date for the log which could help with troubleshooting. If we have failures, we might see stuff like this:
\n
![\"\"](\"https:\/\/i0.wp.com\/practicalpowershell.com\/wp-content\/uploads\/2021\/01\/PSTOTW-2021-01-25-02.jpg?ssl=1\")
<\/a>\nWith this log, we see that here were some connectivity issues, we might notice that there was an Internet issue at that time to explain it and if not, then may something more local that needs investigating.<\/p>\n
Summary<\/h3>\n
As we see, this form of logging has its advantages (additional information) and downsides (additional time to code). The formatting that is chosen is entirely up to you the scripter. You can add more or remove lines, use different date formats and more. Entirely up to you how the log will log as it will be yours to use. Hope you enjoyed this tip. Sign up for the newsletter if you have not already!<\/p>\n","protected":false},"excerpt":{"rendered":"
Log Files Creating log files for auditing can be a pain to implement, but may be a boon if you are automating scripts. The oft asked detail, is indeed, how much details do we need to log for the script? Well. It Depends. How deep do you want the log to cover? Do you just […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":[],"rop_publish_now_history":[],"rop_publish_now_status":"pending","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[22],"tags":[],"class_list":["post-3825","post","type-post","status-publish","format-standard","hentry","category-powershell"],"yoast_head":"\n