<?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: Which DPL syntax is applicable? in DQL</title>
    <link>https://community.dynatrace.com/t5/DQL/Which-DPL-syntax-is-applicable/m-p/232909#M476</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/64547"&gt;@WellPP&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;You can try to add :&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| parse content, "LD 'is' STRING:VARIABLENAME"
| fields VARIABLENAME&lt;/LI-CODE&gt;&lt;P&gt;Let me know it's work &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 27 Dec 2023 17:40:49 GMT</pubDate>
    <dc:creator>gbaudart</dc:creator>
    <dc:date>2023-12-27T17:40:49Z</dc:date>
    <item>
      <title>Which DPL syntax is applicable?</title>
      <link>https://community.dynatrace.com/t5/DQL/Which-DPL-syntax-is-applicable/m-p/231827#M421</link>
      <description>&lt;P&gt;I am creating a processing rule through MATCHER:&lt;/P&gt;&lt;P&gt;matchesPhrase(content, "setFinalReturnCustomerState") AND dt.entity.cloud_application == "CLOUD_APPLICATION-"&lt;/P&gt;&lt;P&gt;I get the log line that has the content:&lt;/P&gt;&lt;P&gt;{&lt;BR /&gt;"@timestamp": "2023-12-13T20:06:07.833+00:00",&lt;BR /&gt;"level": "INFO",&lt;BR /&gt;"severity": "INFO",&lt;BR /&gt;"service": "customer",&lt;BR /&gt;"message": "setFinalReturnCustomerState - Customer 11111111111 is Active Open Sea",&lt;BR /&gt;"stack_trace": ""&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;I need the information that comes after "is", which could be: Quarantine, Open Sea, No Open Sea.&lt;/P&gt;&lt;P&gt;With this I will create a processing rule for this to become a dimension in my metric. I tried to use DPL Arquiteto but I was not successful in the syntax.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 20:55:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/Which-DPL-syntax-is-applicable/m-p/231827#M421</guid>
      <dc:creator>WellPP</dc:creator>
      <dc:date>2023-12-13T20:55:48Z</dc:date>
    </item>
    <item>
      <title>Re: Which DPL syntax is applicable?</title>
      <link>https://community.dynatrace.com/t5/DQL/Which-DPL-syntax-is-applicable/m-p/232909#M476</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/64547"&gt;@WellPP&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;You can try to add :&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| parse content, "LD 'is' STRING:VARIABLENAME"
| fields VARIABLENAME&lt;/LI-CODE&gt;&lt;P&gt;Let me know it's work &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Dec 2023 17:40:49 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/Which-DPL-syntax-is-applicable/m-p/232909#M476</guid>
      <dc:creator>gbaudart</dc:creator>
      <dc:date>2023-12-27T17:40:49Z</dc:date>
    </item>
    <item>
      <title>Re: Which DPL syntax is applicable?</title>
      <link>https://community.dynatrace.com/t5/DQL/Which-DPL-syntax-is-applicable/m-p/233093#M486</link>
      <description>&lt;P&gt;Actually I would have even do one more step and parsing the content into a JSON object so that you're sure you're parsing only the message itself. something like:&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;| parse content, "JSON:parsedJsonObj"
| parse parsedJsonObj[message],  "LD 'is' STRING:customerName"
| fieldsRemove parsedJsonObj&lt;/LI-CODE&gt;</description>
      <pubDate>Mon, 01 Jan 2024 07:33:45 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/DQL/Which-DPL-syntax-is-applicable/m-p/233093#M486</guid>
      <dc:creator>gilgi</dc:creator>
      <dc:date>2024-01-01T07:33:45Z</dc:date>
    </item>
  </channel>
</rss>

