Workflows for parsing DQL results and triggering conditional branches

wolfgang_heider — Tue, 30 Jul 2024 12:35:19 GMT

Hello Dynatrace Community,

Welcome to the third article from the series presenting useful Workflows for you and your everyday work. This time, we’ll take a closer look at how we can automate parsing DQL and how we can trigger other tasks based on the results.

In the first sample, you can:

Trigger manually (or with API) the workflow to get the error count by Kubernetes namespace in your environment through the DQL query

Create a new trigger for specific tasks, based on the results, if:

the error count is too high

status of the production is ok

the product namespace can’t be found

The second workflow has the same results and the use case, but this time, it adds another step with JavaScript, which iterates through the results JSON array. This way, you’ll get the additional flexibility for your workflow, that you can edit for your needs.

Both samples are in ours Github repository. Download them and check them out in your Dynatrace environment.

If you have some creative ideas how to expand on those workflows, let us know! This GitHub repository is community-driven, and it’s here for you and your workflows and contributions. Help others use automation in Dynatrace to the fullest and learn its features and possibilities along the way.

topic Workflows for parsing DQL results and triggering conditional branches in Custom Solutions Spotlight

Workflows for parsing DQL results and triggering conditional branches