<?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 DQL for Successful vs Failed Product Transfers by brand (Logs on Grail vs Classic) in DQL</title>
    <link>https://community.dynatrace.com/t5/DQL/DQL-for-Successful-vs-Failed-Product-Transfers-by-brand-Logs-on/m-p/290913#M2842</link>
    <description>&lt;DIV&gt;We need to chart Successful vs Failed requests per brand from application logs. The brands are logged in the message body (JSON fragments like "brand":"Bradford"), and success is indicated by "offerAccepted":"Y". This is the example output below — it should look like this:&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="arunshetty2281_0-1764941025695.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/31117iBF6057136F7E86FB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="arunshetty2281_0-1764941025695.png" alt="arunshetty2281_0-1764941025695.png" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;In Grail/DQL, we can parse and aggregate in a single query. In Logs &amp;amp; Events Classic, we understand aggregation requires Log Processing + Log Metrics rather than inline summarize. I’d like to confirm the best practice for both, and validate the parse/aggregation approach. (Docs I’ve consulted: DQL matcher &amp;amp; parsing, aggregation commands, and Classic Log Monitoring guidance.)&lt;/DIV&gt;</description>
    <pubDate>Fri, 05 Dec 2025 13:23:52 GMT</pubDate>
    <dc:creator>arunshetty2281</dc:creator>
    <dc:date>2025-12-05T13:23:52Z</dc:date>
    <item>
      <title>DQL for Successful vs Failed Product Transfers by brand (Logs on Grail vs Classic)</title>
      <link>https://community.dynatrace.com/t5/DQL/DQL-for-Successful-vs-Failed-Product-Transfers-by-brand-Logs-on/m-p/290913#M2842</link>
      <description>&lt;DIV&gt;We need to chart Successful vs Failed requests per brand from application logs. The brands are logged in the message body (JSON fragments like "brand":"Bradford"), and success is indicated by "offerAccepted":"Y". This is the example output below — it should look like this:&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="arunshetty2281_0-1764941025695.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/31117iBF6057136F7E86FB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="arunshetty2281_0-1764941025695.png" alt="arunshetty2281_0-1764941025695.png" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;In Grail/DQL, we can parse and aggregate in a single query. In Logs &amp;amp; Events Classic, we understand aggregation requires Log Processing + Log Metrics rather than inline summarize. I’d like to confirm the best practice for both, and validate the parse/aggregation approach. (Docs I’ve consulted: DQL matcher &amp;amp; parsing, aggregation commands, and Classic Log Monitoring guidance.)&lt;/DIV&gt;</description>
      <pubDate>Fri, 05 Dec 2025 13:23:52 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/DQL-for-Successful-vs-Failed-Product-Transfers-by-brand-Logs-on/m-p/290913#M2842</guid>
      <dc:creator>arunshetty2281</dc:creator>
      <dc:date>2025-12-05T13:23:52Z</dc:date>
    </item>
    <item>
      <title>Re: DQL for Successful vs Failed Product Transfers by brand (Logs on Grail vs Classic)</title>
      <link>https://community.dynatrace.com/t5/DQL/DQL-for-Successful-vs-Failed-Product-Transfers-by-brand-Logs-on/m-p/290964#M2847</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/95565"&gt;@arunshetty2281&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regarding the Log Classic I can confirm that first you should parse out the brand and offerAccepted by log processing, then you can generate a log attribute from them. Finally you should create a log metric (count of occurance) and use this log attributes as dimension of this metric. Then you can create a table in the data explorer from the log metric split by these two dimensions:&amp;nbsp; first entity selector split by the two dimensions the filter to offerAccepted dimension with Y and the second entity selector should be the same but filter to offerAccepted dimension with N.&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;János&lt;/P&gt;</description>
      <pubDate>Sat, 06 Dec 2025 22:03:30 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/DQL-for-Successful-vs-Failed-Product-Transfers-by-brand-Logs-on/m-p/290964#M2847</guid>
      <dc:creator>Mizső</dc:creator>
      <dc:date>2025-12-06T22:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: DQL for Successful vs Failed Product Transfers by brand (Logs on Grail vs Classic)</title>
      <link>https://community.dynatrace.com/t5/DQL/DQL-for-Successful-vs-Failed-Product-Transfers-by-brand-Logs-on/m-p/295627#M3194</link>
      <description>&lt;P&gt;Thanks for the solution. I will try that&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2026 12:13:44 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/DQL-for-Successful-vs-Failed-Product-Transfers-by-brand-Logs-on/m-p/295627#M3194</guid>
      <dc:creator>arunshetty2281</dc:creator>
      <dc:date>2026-03-04T12:13:44Z</dc:date>
    </item>
  </channel>
</rss>

