remedy ticket not generating after DQL query result

[vijaypalve]

hi Team,

We are utilizing the ServiceBroker action (‘Create Incident & 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.

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.

fetch logs, from: -60m
| filter matchesPhrase(index, "myindexname")

| parse content, """LD "'job_name':" SPACE SQS:job_name"""
| fieldsAdd container_name = splitString(source, "/")[-2]
| fieldsAdd interface_name_temp= splitString(source, "/")[-1]
| fieldsAdd interface_name= splitString(interface_name_temp,".")[0]
| filter container_name== "raw-to-c3" and interface_name == "billing_transfer"
| dedup host,container_name,interface_name
| fields host,container_name,interface_name"

need help to resolve above issue. not sure, what I am doing wrong here.

[marco_irmer]

I am not familiar with the "Create Incident & send to Service Broker" workflow action. Is this action part of a connector provided by Dynatrace or something custom?

[vijaypalve]

it is provided by dynatrace.