How to remap impacted entity reported as Tenant / Environment ?

[DanielS]

Hello, I find that in many problems, the impacted entity is the tenant / environment. This happens with SLOs, log alerts, among others.

Looking for a way to remap these to the corresponding or desired entity, I configured two properties in the metrics events:

• dt.event.allow_entity_remapping with a value of true
• dt.event.source where I specify the desired entity.

Although when the issue occurs, the dt.event.source entity is reported in the description, I still see the environment as impacted, and this doesn't help the troubleshooting teams.

Has anyone managed to change this via some property I'm not familiar with? 

Thank you very much.

[Peter_Youssef]

Hello @DanielS 

Thanks for sharing exposed scenario, till we get an applicable solution a product idea can be raised to speed up the resolution process.

Hoping it helps.

BR,

Peter

[DanielS]

Thanks, @Peter_Youssef before I proceed to an idea I want to be sure that I am not missing something. Also I want to understand why the "dt.event.allow_entity_remapping", doesn't work, because I can see that this flag defines whether the remapping of the target entity is enabled (true) or disabled (false). If the remapping is enabled, Dynatrace can map the event to an entity extracted from the event metadata. If the remapping is disabled or the extraction is not possible, Dynatrace maps the event to the entity specified in the event configuration (for example, a specific host) or to the global environment entity. This property can be written by most event sources, such as Events API, metric events, log events, or Extension 1.0 events.

So maybe could be a bug, or me.

[Peter_Youssef]

Thanks @DanielS for your feedback, agree with you sir 🤝🙂

[helton_harada]

We faced a similar situation when we configured a metric event for a extension metric (tibco queue depth).

In our case, we added a property with a "dt.entity.tibco.queue" as a "dimension key of entity for events".

After that, problems were raised with "Entity"(the one we set before) Impacted Level instead of "Environment" impact level.

[Yosi_Neuman]

Hi @DanielS

Did you check what dt.event.entity_remapping_failure_info holds? as described under troubleshooting of Event topology extraction and mapping

HTH

Yos