Release monitoring for applications?

[Dani_l]

Hi community,

In our company we’re having multiple SaaS application which we’re monitoring with agentless RUM. For some application we can do “configuration releases” via an automated pipeline. We were hoping to use the custom event ingestion to register the release into Dynatrace as well. Looking at the documentation and doing a small test the release monitoring only seems to be possible for PROCESS_GROUP_INSTANCE. Is there a way to use this for other type of entities?

Reasons for doing this: one place having all releases/config changes registration and secondly we want to feed Davis AI with as much as info possible hoping it can correlate application issues also with releases.

Looking forward seeing your response,

Kind regards,

Daan

Fyi the example event according to the docs:

{

“eventType”: “CUSTOM_DEPLOYMENT”,

“title”: “Easytravel 1.1”,

“entitySelector”: “type(PROCESS_GROUP_INSTANCE),tag(easytravel)”,

“properties”: {

“dt.event.deployment.name”:“Easytravel 1.1”,

“dt.event.deployment.version”: “1.1”,

“dt.event.deployment.release_stage”: “production” ,

“dt.event.deployment.release_product”: “frontend”,

“dt.event.deployment.release_build_version”: “123”,

“approver”: “Jason Miller”,

“dt.event.deployment.ci_back_link”: https://pipelines/easytravel/123,

“gitcommit”: “e5a6baac7eb”,

“change-request”: “CR-42”,

“dt.event.deployment.remediation_action_link”: https://url.com,

“dt.event.is_rootcause_relevant”: true

}

}

[cv_dewr]

Hi Daan, have you tried changing the entitySelector value to something like

type(APPLICATION),tag(myapptag)

or

type(APPLICATION),name(myappname)

Can you show us what you have tried?

[Dani_l]

Hi cv_dewr,

Thanks for you comment. I tried yesterday with the options you’ve indicated and gave it another try this morning with a fresh mind.

I’ve made some progress but it’s not yet what I fully expect. First, using the exact example in the docs, and replacing only the first part with “type(APPLICATION),tag(myapptag)” gave an 201 response and no info in Dynatrace was visible:

<span>{</span>  <span class="">"eventIngestResults"</span><span>: [</span>    {
      <span class="">"correlationId"</span><span>: </span><span>"string"</span><span>,</span>      <span class="">"status"</span><span>: </span><span>"INVALID_ENTITY_TYPE"</span>
    }
  ],
  <span class="">"reportCount"</span><span>: </span><span>0</span>
}

This morning I did another try with the same and noticed another error: “code”: 400,
“message”: “Could not map JSON at ‘properties’ near line 12 column 47”. After fixing somehow some missing quotes it was successful and a event has been created with a correlationID.

However the deployment info is only as an event within the application and there’s no entry being made in the release page. I would expect the release update would be visible over there (having one complete overview on all deployments done in the environment).

I appreciate your help in this.

Kind regards,

Daan

[izabelarokita]

Hey @Daniël, did you manage to find the solution to your problem? If so, it would be amazing if you’ve shared it with the rest of the Community! If not, let me know, and I’ll look for some further assistance 😊

[StrangerThing]

The CUSTOM_DEPLOYMENT event type will not show up on the Releases app for some reason. We are having to use the event plus setting some environment variables on our process instances. When we do that, we get the “release” in the Releases app.

Honestly we’ve stopped using the Releases app for this reason and started simply querying the events themselves in our own view(s) on a Notebook or Dashboard. I’m not sure how the environment variables would work on agentless RUM, but maybe worth looking into.

[Dani_l]

Hi @IzabelaRokita,

No unfortunately we didn’t solve the issue and therefore we lack one overview within the release monitoring functionality. For the parts (read procesgroups) which we do have in the release monitoring we’re having trouble to let Davis point to a release deployment as a rootcause when deliberately causing issues in a release (eg failures or bad performance).

Perhaps the functionality is limited in managed environments but in general the functionality isn’t what we would expect from it.

Looking forward  for a response in this matter.

Kind regards,

Daan

[fvillagran]

Hi everyone.Here i have an example of CUSTOM_DEPLOYMENT.I hope it helps you.The most important thing is entitySelector{  “eventType”: “CUSTOM_DEPLOYMENT”,  “title”: “Despliegue de la versión 0.0.21 prueba 005”,  “entitySelector”: “type(PROCESS_GROUP_INSTANCE),entityName(\“SpringBoot com.example.demo.DemoApplication\”)”,  “properties”: {    “dt.event.deployment.name”:“Process SpringBoot com.example.demo.DemoApplication deployed”,    “dt.event.deployment.version”: “0.0.21”,    “dt.event.deployment.project”: “demo”,    “dt.event.deployment.release_stage”: “dev”,    “dt.event.deployment.release_product”: “demo”,    “dt.event.deployment.release_build_version”: “0.0.21.20250710.1152”,    “approver”: “Francisco Villagrán”,    “dt.event.deployment.ci_back_link”: “http://localhost:8080/job/Pipeline_Java_Demo”,    “gitcommit”: “e5a6baac7eb”,    “change-request”: “CR-42”,    “dt.event.deployment.remediation_action_link”: “https://url.com”,    “dt.event.is_rootcause_relevant”: true  }}

[Dani_l]

Thanks for your inputs!

I’m able to create deploymentevents (automated or via custom events) however I’m not able to:

- get Davis to point the rootcause to a deployment (especially if “dt.event.is_rootcause_relevant”: true has been set)

- get the deployment events on application level (not procesgroup lvl) also in the release monitoring page so there’s one single view (and truth) on release changes in our own IT or SaaS applications changes.

I hope this clarifies my issue,

Kind regards,

Daan