Dynatrace / Dynatrace/community-examples

Cloud SRE Agents: Problems not dispatched when smartscape.affected_entities is empty in workflow trigger payload

Open
#46 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HCL
Stars
17
Forks
12
Avg merge
13m
Merged PRs (30d)
6

Description

**This is a known Issue on Dynatrace end**

In certain cases, Problem events are triggered without entity IDs, e.g.:
```
{
"event.id": "P-2609031",
"event.name": "Unexpected high load",
"event.category": "RESOURCE_CONTENTION",
"event.status": "ACTIVE",
"event.status_transition": "UPDATED",
"dt.analysis.ready": true,
"smartscape.affected_entities": [],
"affected_entity_ids": null
}
```

In such a case, the **Investigation** Workflow is triggered, but will not forward the problem to any Cloud Provider, as we cannot reliably determine which cloud provider this problem is associated with.

We will find a log like this (e.g., `fetch logs | filter dt.app.id == "community.cloudsreagents"`)
```
[Step 3] No affected entities found.
```

Contributor guide

Open the contributing guide

Research direction

Start with the Investigation Workflow and inspect the Step 3 path that logs "No affected entities found." Reproduce or trace the payload where smartscape.affected_entities is empty and affected_entity_ids is null. Done should be defined as an agreed behavior for these events, including whether and how the problem can be forwarded to a cloud provider.

Written by the indexing model from the issue text.

Assessment

Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.