<?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: DLT Event Logs in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/dlt-event-logs/m-p/76959#M35363</link>
    <description>&lt;P&gt;Hi !&amp;nbsp;&lt;/P&gt;&lt;P&gt;The cost field under &lt;EM&gt;planning_information&lt;/EM&gt; in your DLT (Delta Live Tables) workflow system event logs represents an estimated cost for the particular maintenance type operation. In this context, &lt;EM&gt;MAINTENANCE_TYPE_COMPLETE_RECOMPUTE&lt;/EM&gt; indicates that a complete recompute operation is planned, and the cost value (48.0) likely signifies the estimated computational cost for this operation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Explanation of Fields&lt;/STRONG&gt;:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;maintenance_type&lt;/STRONG&gt;: Type of maintenance operation being performed.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;is_chosen&lt;/STRONG&gt;: Indicates if this technique was chosen for execution.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;is_applicable&lt;/STRONG&gt;: Indicates if this technique is applicable to the current scenario.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;cost&lt;/STRONG&gt;: Estimated computational cost for this maintenance operation.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;table_id&lt;/STRONG&gt;: Identifier for the target table on which this maintenance operation is performed.&lt;/P&gt;</description>
    <pubDate>Fri, 05 Jul 2024 23:36:57 GMT</pubDate>
    <dc:creator>mtajmouati</dc:creator>
    <dc:date>2024-07-05T23:36:57Z</dc:date>
    <item>
      <title>DLT Event Logs</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-event-logs/m-p/76953#M35362</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Does anyone know what &lt;U&gt;&lt;EM&gt;details:planning_information:technique_information[0]:cost&lt;/EM&gt;&lt;/U&gt;&amp;nbsp;under planning_information event type means in my DLT workflow system event logs? For context, I'm trying to track the cost per run&amp;nbsp;of my DLT workflow and I do not have Unity Catalog enabled.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jul 2024 21:11:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-event-logs/m-p/76953#M35362</guid>
      <dc:creator>Djelany</dc:creator>
      <dc:date>2024-07-05T21:11:43Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Event Logs</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-event-logs/m-p/76959#M35363</link>
      <description>&lt;P&gt;Hi !&amp;nbsp;&lt;/P&gt;&lt;P&gt;The cost field under &lt;EM&gt;planning_information&lt;/EM&gt; in your DLT (Delta Live Tables) workflow system event logs represents an estimated cost for the particular maintenance type operation. In this context, &lt;EM&gt;MAINTENANCE_TYPE_COMPLETE_RECOMPUTE&lt;/EM&gt; indicates that a complete recompute operation is planned, and the cost value (48.0) likely signifies the estimated computational cost for this operation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Explanation of Fields&lt;/STRONG&gt;:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;maintenance_type&lt;/STRONG&gt;: Type of maintenance operation being performed.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;is_chosen&lt;/STRONG&gt;: Indicates if this technique was chosen for execution.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;is_applicable&lt;/STRONG&gt;: Indicates if this technique is applicable to the current scenario.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;cost&lt;/STRONG&gt;: Estimated computational cost for this maintenance operation.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;table_id&lt;/STRONG&gt;: Identifier for the target table on which this maintenance operation is performed.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jul 2024 23:36:57 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-event-logs/m-p/76959#M35363</guid>
      <dc:creator>mtajmouati</dc:creator>
      <dc:date>2024-07-05T23:36:57Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Event Logs</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-event-logs/m-p/77148#M35406</link>
      <description>&lt;P&gt;Thank you!&amp;nbsp;A quick follow up question, is there a way to track the full cost of the run by querying the system event logs instead of just the maintenance cost? Or is that only possible by querying the billable usage path in S3 (in my case)?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2024 13:00:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-event-logs/m-p/77148#M35406</guid>
      <dc:creator>Djelany</dc:creator>
      <dc:date>2024-07-08T13:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Event Logs</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-event-logs/m-p/88832#M37633</link>
      <description>&lt;P&gt;you can enable system.billing schema and see the costs of the runs from the usage table.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Sep 2024 07:43:36 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-event-logs/m-p/88832#M37633</guid>
      <dc:creator>adriennn</dc:creator>
      <dc:date>2024-09-06T07:43:36Z</dc:date>
    </item>
  </channel>
</rss>

