<?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 Remedy ticket isn't generating after DQL query returns result of zero in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Remedy-ticket-isn-t-generating-after-DQL-query-returns-result-of/m-p/279502#M5706</link>
    <description>&lt;P&gt;hi Team,&lt;/P&gt;
&lt;P&gt;We are utilizing the ServiceBroker action (‘Create Incident &amp;amp; Send to Service Broker’) to automatically generate a Remedy incident when a DQL query returns a result of zero. However, the expected incident is not being generated.&lt;/P&gt;
&lt;P&gt;The intended functionality is that whenever a Docker process becomes stuck, a Remedy incident should be triggered, specifying the reason for failure and the corresponding job name. To achieve this, we have implemented ServiceBroker and formulated the following DQL query. If logs exist within the last 60 minutes, no incident is required. However, if the query returns a result of ‘0’[Zero], it should initiate a Remedy incident. Currently, this expected behavior is not occurring.&lt;/P&gt;
&lt;P&gt;fetch logs, from: -60m&lt;BR /&gt;| filter matchesPhrase(index, "myindexname")&lt;/P&gt;
&lt;P&gt;| parse content, """LD "'job_name':" SPACE SQS:job_name"""&lt;BR /&gt;| fieldsAdd container_name = splitString(source, "/")[-2]&lt;BR /&gt;| fieldsAdd interface_name_temp= splitString(source, "/")[-1]&lt;BR /&gt;| fieldsAdd interface_name= splitString(interface_name_temp,".")[0]&lt;BR /&gt;| filter container_name== "raw-to-c3" and interface_name == "billing_transfer"&lt;BR /&gt;| dedup host,container_name,interface_name&lt;BR /&gt;| fields host,container_name,interface_name"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vijaypalve_1-1750069708782.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/28518iF1B3E4E087276543/image-size/medium?v=v2&amp;amp;px=400" role="button" title="vijaypalve_1-1750069708782.png" alt="vijaypalve_1-1750069708782.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;need help to resolve above issue. not sure, what I am doing wrong here.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 18 Dec 2025 14:05:40 GMT</pubDate>
    <dc:creator>vijaypalve</dc:creator>
    <dc:date>2025-12-18T14:05:40Z</dc:date>
    <item>
      <title>Remedy ticket isn't generating after DQL query returns result of zero</title>
      <link>https://community.dynatrace.com/t5/Alerting/Remedy-ticket-isn-t-generating-after-DQL-query-returns-result-of/m-p/279502#M5706</link>
      <description>&lt;P&gt;hi Team,&lt;/P&gt;
&lt;P&gt;We are utilizing the ServiceBroker action (‘Create Incident &amp;amp; Send to Service Broker’) to automatically generate a Remedy incident when a DQL query returns a result of zero. However, the expected incident is not being generated.&lt;/P&gt;
&lt;P&gt;The intended functionality is that whenever a Docker process becomes stuck, a Remedy incident should be triggered, specifying the reason for failure and the corresponding job name. To achieve this, we have implemented ServiceBroker and formulated the following DQL query. If logs exist within the last 60 minutes, no incident is required. However, if the query returns a result of ‘0’[Zero], it should initiate a Remedy incident. Currently, this expected behavior is not occurring.&lt;/P&gt;
&lt;P&gt;fetch logs, from: -60m&lt;BR /&gt;| filter matchesPhrase(index, "myindexname")&lt;/P&gt;
&lt;P&gt;| parse content, """LD "'job_name':" SPACE SQS:job_name"""&lt;BR /&gt;| fieldsAdd container_name = splitString(source, "/")[-2]&lt;BR /&gt;| fieldsAdd interface_name_temp= splitString(source, "/")[-1]&lt;BR /&gt;| fieldsAdd interface_name= splitString(interface_name_temp,".")[0]&lt;BR /&gt;| filter container_name== "raw-to-c3" and interface_name == "billing_transfer"&lt;BR /&gt;| dedup host,container_name,interface_name&lt;BR /&gt;| fields host,container_name,interface_name"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vijaypalve_1-1750069708782.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/28518iF1B3E4E087276543/image-size/medium?v=v2&amp;amp;px=400" role="button" title="vijaypalve_1-1750069708782.png" alt="vijaypalve_1-1750069708782.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;need help to resolve above issue. not sure, what I am doing wrong here.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Dec 2025 14:05:40 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Remedy-ticket-isn-t-generating-after-DQL-query-returns-result-of/m-p/279502#M5706</guid>
      <dc:creator>vijaypalve</dc:creator>
      <dc:date>2025-12-18T14:05:40Z</dc:date>
    </item>
    <item>
      <title>Re: remedy ticket not generating after DQL query result</title>
      <link>https://community.dynatrace.com/t5/Alerting/Remedy-ticket-isn-t-generating-after-DQL-query-returns-result-of/m-p/279550#M5711</link>
      <description>&lt;P&gt;I am not familiar with the "Create Incident &amp;amp; send to Service Broker" workflow action. Is this action part of a connector provided by Dynatrace or something custom?&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jun 2025 17:49:49 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Remedy-ticket-isn-t-generating-after-DQL-query-returns-result-of/m-p/279550#M5711</guid>
      <dc:creator>marco_irmer</dc:creator>
      <dc:date>2025-06-16T17:49:49Z</dc:date>
    </item>
    <item>
      <title>Re: remedy ticket not generating after DQL query result</title>
      <link>https://community.dynatrace.com/t5/Alerting/Remedy-ticket-isn-t-generating-after-DQL-query-returns-result-of/m-p/279587#M5712</link>
      <description>&lt;P&gt;it is provided by dynatrace.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vijaypalve_0-1750145883066.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/28535i9FE1809F2EE3BBCE/image-size/medium?v=v2&amp;amp;px=400" role="button" title="vijaypalve_0-1750145883066.png" alt="vijaypalve_0-1750145883066.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jun 2025 07:38:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Remedy-ticket-isn-t-generating-after-DQL-query-returns-result-of/m-p/279587#M5712</guid>
      <dc:creator>vijaypalve</dc:creator>
      <dc:date>2025-06-17T07:38:17Z</dc:date>
    </item>
  </channel>
</rss>

