<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Logging Infrastructure within PowerShell Toolkit in Microsoft Virtualization Discussions</title>
    <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Logging-Infrastructure-within-PowerShell-Toolkit/m-p/61301#M3046</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The toolkit is just that a toolkit.&amp;nbsp; It is not an application, it's a low level building block that enables you to build your own custom solutions. Each individual cmdlet has standard warning/error/debug/info information, but that information is written to the PowerShell host, not a common log.&amp;nbsp;&amp;nbsp; If your solutions require a logging infrastructure, you can build one into your scripts using standard cmdlets like New-Event, and out-file. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps, &lt;/P&gt;&lt;P&gt;~Glenn &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Dec 2011 13:30:06 GMT</pubDate>
    <dc:creator>GlennSizemore</dc:creator>
    <dc:date>2011-12-22T13:30:06Z</dc:date>
    <item>
      <title>Logging Infrastructure within PowerShell Toolkit</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Logging-Infrastructure-within-PowerShell-Toolkit/m-p/61295#M3045</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please guide me if there is any logging infrastructure within PowerShell Toolkit to capture events/info/warnings/errors or cmdlet parameters. If yes, how to enable &amp;amp; configure it.&lt;/P&gt;&lt;P&gt;I mean log for all the activities that happen in PowerShell Toolkit, such a what cmdlets the user has run, what warnings occured, etc. (like a normal logging infrastructure for any good application).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:39:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Logging-Infrastructure-within-PowerShell-Toolkit/m-p/61295#M3045</guid>
      <dc:creator>TEAMHELPID</dc:creator>
      <dc:date>2025-06-05T06:39:08Z</dc:date>
    </item>
    <item>
      <title>Re: Logging Infrastructure within PowerShell Toolkit</title>
      <link>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Logging-Infrastructure-within-PowerShell-Toolkit/m-p/61301#M3046</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The toolkit is just that a toolkit.&amp;nbsp; It is not an application, it's a low level building block that enables you to build your own custom solutions. Each individual cmdlet has standard warning/error/debug/info information, but that information is written to the PowerShell host, not a common log.&amp;nbsp;&amp;nbsp; If your solutions require a logging infrastructure, you can build one into your scripts using standard cmdlets like New-Event, and out-file. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps, &lt;/P&gt;&lt;P&gt;~Glenn &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Dec 2011 13:30:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/Logging-Infrastructure-within-PowerShell-Toolkit/m-p/61301#M3046</guid>
      <dc:creator>GlennSizemore</dc:creator>
      <dc:date>2011-12-22T13:30:06Z</dc:date>
    </item>
  </channel>
</rss>

