<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Logging on Rob Sewell (aka SQL DBA With A Beard)</title><link>https://blog.robsewell.com/tags/logging/</link><description>Recent content in Logging on Rob Sewell (aka SQL DBA With A Beard)</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 09 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.robsewell.com/tags/logging/index.xml" rel="self" type="application/rss+xml"/><item><title>MicrosoftFabricMgmt: Structured Logging with PSFramework</title><link>https://blog.robsewell.com/blog/microsoftfabricmgmt-psframework-logging/</link><pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate><guid>https://blog.robsewell.com/blog/microsoftfabricmgmt-psframework-logging/</guid><description>&lt;img src="https://blog.robsewell.com/assets/uploads/2026/03/Getpsfmessage.png" alt="Featured image of post MicrosoftFabricMgmt: Structured Logging with PSFramework" /&gt;&lt;h2 id="introduction"&gt;Introduction
&lt;/h2&gt;&lt;p&gt;If you have ever come back to a script the next morning and thought &amp;ldquo;what on earth happened last night?&amp;rdquo;, you understand why logging matters. &lt;code&gt;Write-Host&lt;/code&gt; and &lt;code&gt;Write-Verbose&lt;/code&gt; are fine for interactive use, but in automation — scheduled tasks, CI/CD pipelines, long-running jobs — you need something more structured. Something you can query, filter, and persist across sessions, something that you can provide to your team or support or auditors.&lt;/p&gt;</description></item></channel></rss>