<?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: Best practices to query logs in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/best-practices-to-query-logs/m-p/26222#M18330</link>
    <description>And if it is generic logs which gets landed on S3 , it'd be worth taking a look at Autoloader. Here is a blog post on processing crowdstrike logs in a similar way</description>
    <pubDate>Mon, 07 Jun 2021 14:14:00 GMT</pubDate>
    <dc:creator>sajith_appukutt</dc:creator>
    <dc:date>2021-06-07T14:14:00Z</dc:date>
    <item>
      <title>Best practices to query logs</title>
      <link>https://community.databricks.com/t5/data-engineering/best-practices-to-query-logs/m-p/26220#M18328</link>
      <description>&lt;P&gt;We dump our logs in S3 currently. Can you give us best practices to make these logs easier to query?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jun 2021 19:48:09 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/best-practices-to-query-logs/m-p/26220#M18328</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2021-06-04T19:48:09Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices to query logs</title>
      <link>https://community.databricks.com/t5/data-engineering/best-practices-to-query-logs/m-p/26221#M18329</link>
      <description>If you mean Databricks Audit Logs, you can see example code for easy querying/integration here!&lt;BR /&gt;&lt;A href="https://docs.databricks.com/administration-guide/account-settings/audit-logs.html#analyze-audit-logs" target="test_blank"&gt;https://docs.databricks.com/administration-guide/account-settings/audit-logs.html#analyze-audit-logs&lt;/A&gt;</description>
      <pubDate>Mon, 07 Jun 2021 14:07:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/best-practices-to-query-logs/m-p/26221#M18329</guid>
      <dc:creator>User16783855117</dc:creator>
      <dc:date>2021-06-07T14:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices to query logs</title>
      <link>https://community.databricks.com/t5/data-engineering/best-practices-to-query-logs/m-p/26222#M18330</link>
      <description>And if it is generic logs which gets landed on S3 , it'd be worth taking a look at Autoloader. Here is a blog post on processing crowdstrike logs in a similar way</description>
      <pubDate>Mon, 07 Jun 2021 14:14:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/best-practices-to-query-logs/m-p/26222#M18330</guid>
      <dc:creator>sajith_appukutt</dc:creator>
      <dc:date>2021-06-07T14:14:00Z</dc:date>
    </item>
  </channel>
</rss>

