<?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: Lost monitoring details for notebook in Data Engineering</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4770687#M11108</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="883010" data-lia-user-login="v-saisrao-msft" class="lia-mention lia-mention-user"&gt;v-saisrao-msft&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What resource are you referring to when you mention a table.&amp;nbsp; A Data Warehouse table?&amp;nbsp; That seems like a pretty expensive way to solve the problem&lt;BR /&gt;&lt;BR /&gt;I will probably dump to temp tables in a lakehouse or something.&lt;BR /&gt;&lt;BR /&gt;Ideally there would be a way to preserve Spark monitoring logs, regardless of whether the notebooks are temporarily removed.&amp;nbsp; Is it possible that Microsoft doesn't realize the importance of preserving operational logs?&lt;/P&gt;</description>
    <pubDate>Mon, 21 Jul 2025 12:21:27 GMT</pubDate>
    <dc:creator>dbeavon3</dc:creator>
    <dc:date>2025-07-21T12:21:27Z</dc:date>
    <item>
      <title>Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4768914#M11057</link>
      <description>&lt;P&gt;I downloaded, deleted then uploaded a notebook with a new name (ipynb).&amp;nbsp; ... It is largely identical.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How do I find the Monitor activity for those spark sessions the pre-date this change?&amp;nbsp; Is it gone forever?&amp;nbsp; I guess it wouldn't surprise me.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Seems like Fabric shouldn't be so cavalier about blowing away the entire history of jobs running on spark.&amp;nbsp; I suppose I should have added some sort of additional KQL logging functionality?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jul 2025 18:59:42 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4768914#M11057</guid>
      <dc:creator>dbeavon3</dc:creator>
      <dc:date>2025-07-18T18:59:42Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4768961#M11061</link>
      <description>&lt;P&gt;Cavalier?&amp;nbsp; LOL Let me tell you how cavalier it is:&amp;nbsp; Fabric just blew up all my partitions on one lakehouse table the other week and changed the table name. Just like that.&amp;nbsp; I guess it was in a bad mood or something.&amp;nbsp;&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&amp;nbsp; All joking aside, probably a dev that pushed by mistake some new code to production that should have gone through testing first, or the testing was so botched that disaster ensued.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Microsoft is working on a fix. So we wait and count the hours.&lt;/P&gt;</description>
      <pubDate>Sat, 19 Jul 2025 00:31:49 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4768961#M11061</guid>
      <dc:creator>Element115</dc:creator>
      <dc:date>2025-07-19T00:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4769014#M11068</link>
      <description>&lt;P&gt;You can get the "Workspace Monitoring"&amp;nbsp; eventhouse if you are willing to pay the extra cost.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In general you should assume that artifact logging is a 30 day window, and there is no SLA whatsoever.&amp;nbsp; Fun fact: The Capacity Metrics App Kusto database has an artificial ingestion limit of 100K operations per 30 second slot.&amp;nbsp; Any halfway busy capacity above F128 can easily blow through that limit, and you end up flying blind for x percent of your operations.&lt;/P&gt;</description>
      <pubDate>Sat, 19 Jul 2025 00:24:20 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4769014#M11068</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2025-07-19T00:24:20Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4769021#M11069</link>
      <description>&lt;P&gt;'Flying blind' would be a great marketing campaign! LOL Which makes me wonder how many enterprise clients are willing to put up with this and for how long.&amp;nbsp; If I were CEO... you can guess how this sentence ends. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 19 Jul 2025 00:34:23 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4769021#M11069</guid>
      <dc:creator>Element115</dc:creator>
      <dc:date>2025-07-19T00:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4769022#M11070</link>
      <description>&lt;P&gt;To their credit Microsoft are willing to listen to our rantings. I don't think they have yet internalized the business ROI centric view&amp;nbsp; (for example our single focus in all this is on CU auditing which seems to be a novel concept for them).&amp;nbsp; We'll see if and how they incorporate our input.&lt;/P&gt;</description>
      <pubDate>Sat, 19 Jul 2025 00:41:29 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4769022#M11070</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2025-07-19T00:41:29Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4769215#M11072</link>
      <description>&lt;P&gt;Yeah, once you delete and re upload the notebook with a new name, the old Spark session history is usually gone. Sadly, Fabric doesn’t keep that history by default. Adding custom KQL logging next time is a smart move to keep track.&lt;/P&gt;</description>
      <pubDate>Sat, 19 Jul 2025 12:13:05 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4769215#M11072</guid>
      <dc:creator>cald147</dc:creator>
      <dc:date>2025-07-19T12:13:05Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4770528#M11101</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="120263" data-lia-user-login="dbeavon3" class="lia-mention lia-mention-user"&gt;dbeavon3&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Thank you&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="1305516" data-lia-user-login="cald147" class="lia-mention lia-mention-user"&gt;cald147&lt;/a&gt;&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="100342" data-lia-user-login="lbendlin" class="lia-mention lia-mention-user"&gt;lbendlin&lt;/a&gt;&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="268213" data-lia-user-login="Element115" class="lia-mention lia-mention-user"&gt;Element115&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please create a logging table to store logs. Once the table is ready, insert a log entry from the notebook, and update this entry after the process completes successfully.&lt;/P&gt;
&lt;P&gt;Since Fabrics deletes logs from monitoring when a notebook is removed, this method can be used as an alternative workaround.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jul 2025 11:11:35 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4770528#M11101</guid>
      <dc:creator>v-saisrao-msft</dc:creator>
      <dc:date>2025-07-21T11:11:35Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4770687#M11108</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="883010" data-lia-user-login="v-saisrao-msft" class="lia-mention lia-mention-user"&gt;v-saisrao-msft&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What resource are you referring to when you mention a table.&amp;nbsp; A Data Warehouse table?&amp;nbsp; That seems like a pretty expensive way to solve the problem&lt;BR /&gt;&lt;BR /&gt;I will probably dump to temp tables in a lakehouse or something.&lt;BR /&gt;&lt;BR /&gt;Ideally there would be a way to preserve Spark monitoring logs, regardless of whether the notebooks are temporarily removed.&amp;nbsp; Is it possible that Microsoft doesn't realize the importance of preserving operational logs?&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jul 2025 12:21:27 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4770687#M11108</guid>
      <dc:creator>dbeavon3</dc:creator>
      <dc:date>2025-07-21T12:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4773486#M11173</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="120263" data-lia-user-login="dbeavon3" class="lia-mention lia-mention-user"&gt;dbeavon3&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;You can choose to use a warehouse, Lakehouse, or SQL database, depending on what database you are using in your model. Consider setting up a logging table in your selected database to store the logs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jul 2025 09:58:34 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4773486#M11173</guid>
      <dc:creator>v-saisrao-msft</dc:creator>
      <dc:date>2025-07-23T09:58:34Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4777773#M11280</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="120263" data-lia-user-login="dbeavon3" class="lia-mention lia-mention-user"&gt;dbeavon3&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-teams="true"&gt;Have you had a chance to review the solution we shared earlier? If the issue persists, feel free to reply so we can help further.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-teams="true"&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jul 2025 04:32:25 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4777773#M11280</guid>
      <dc:creator>v-saisrao-msft</dc:creator>
      <dc:date>2025-07-28T04:32:25Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4779199#M11321</link>
      <description>&lt;P&gt;Doing our own logging shouldn't be the workaround.&amp;nbsp; Microsoft shouldn't just blow away the activity logs for a notebook.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jul 2025 00:02:28 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4779199#M11321</guid>
      <dc:creator>dbeavon3</dc:creator>
      <dc:date>2025-07-29T00:02:28Z</dc:date>
    </item>
    <item>
      <title>Re: Lost monitoring details for notebook</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4780233#M11348</link>
      <description>&lt;P&gt;Ain't that the sorry truth!&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jul 2025 16:44:35 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lost-monitoring-details-for-notebook/m-p/4780233#M11348</guid>
      <dc:creator>Element115</dc:creator>
      <dc:date>2025-07-29T16:44:35Z</dc:date>
    </item>
  </channel>
</rss>

