<?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: How to get log attributes in the Davis Anamoly detection Event Proeperties in DQL</title>
    <link>https://community.dynatrace.com/t5/DQL/How-to-get-log-attributes-in-the-Davis-Anamoly-detection-Event/m-p/261143#M1389</link>
    <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/66475"&gt;@subashsagi41&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It looks like because by the end of the query there are no attributes/dimensions. When using the maketimeseries command without any splits nothing from the logs is retained and the system cannot extract information where there is none. If you run this query in a notebook and visualize it with "Record List" you'll be able to see what's retained.&lt;/P&gt;&lt;P&gt;Also, if you're looking to create an alert based off the logs I'd recommend turning them into a metric using processing rules on ingest. This will allow for cheaper visualization and querying if you don't anticipate it changing much over time.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 31 Oct 2024 01:33:34 GMT</pubDate>
    <dc:creator>Fin_Ubels</dc:creator>
    <dc:date>2024-10-31T01:33:34Z</dc:date>
    <item>
      <title>How to get log attributes in the Davis Anamoly detection Event Proeperties</title>
      <link>https://community.dynatrace.com/t5/DQL/How-to-get-log-attributes-in-the-Davis-Anamoly-detection-Event/m-p/261123#M1385</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I was able to get the dimensions from the metrics but not directly from the logs. Here is my query&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;fetch logs
| filter contains(azure.resource.name, "MTH") and contains(content, "QRY_STATUS") and contains(content, "ETL-ALERT") //and loglevel == "ERROR" 
| parse content, "JSON:json"
| fieldsFlatten json
| fields timestamp, azure.resource.group, APPLICATION_NAME = json.Properties[APPLICATION_NAME], QRY_STATUS = json.Properties[QRY_STATUS], PIPELINESTEPCODE = json.Properties[PIPELINESTEPCODE], 
         TENANT_ID = json.Properties[TENANT_ID], LEVELNUMBER = json.Properties[LEVELNUMBER], QRY_ERROR = json.Properties[QRY_ERROR]
| filter QRY_STATUS == "FAILED"
| makeTimeseries count(), interval: 1m, time: timestamp&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to get the all the attributes in the fields in the event properties, but ,I'm not able to get those.&lt;/P&gt;&lt;P&gt;Any help here is highly appreciated.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 17:41:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/How-to-get-log-attributes-in-the-Davis-Anamoly-detection-Event/m-p/261123#M1385</guid>
      <dc:creator>subashsagi41</dc:creator>
      <dc:date>2024-10-30T17:41:09Z</dc:date>
    </item>
    <item>
      <title>Re: How to get log attributes in the Davis Anamoly detection Event Proeperties</title>
      <link>https://community.dynatrace.com/t5/DQL/How-to-get-log-attributes-in-the-Davis-Anamoly-detection-Event/m-p/261143#M1389</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/66475"&gt;@subashsagi41&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It looks like because by the end of the query there are no attributes/dimensions. When using the maketimeseries command without any splits nothing from the logs is retained and the system cannot extract information where there is none. If you run this query in a notebook and visualize it with "Record List" you'll be able to see what's retained.&lt;/P&gt;&lt;P&gt;Also, if you're looking to create an alert based off the logs I'd recommend turning them into a metric using processing rules on ingest. This will allow for cheaper visualization and querying if you don't anticipate it changing much over time.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Oct 2024 01:33:34 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/How-to-get-log-attributes-in-the-Davis-Anamoly-detection-Event/m-p/261143#M1389</guid>
      <dc:creator>Fin_Ubels</dc:creator>
      <dc:date>2024-10-31T01:33:34Z</dc:date>
    </item>
  </channel>
</rss>

