Dynatrace / Dynatrace/community-examples

CI/CD Observability App - Pipeline Execution Flame Graph redirect error

Open Beginner friendly
#48 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
HCL
Stars
17
Forks
12
Avg merge
13m
Merged PRs (30d)
6

Description

**Describe the bug**
Currently when you click Pipeline Execution Flamegraph, it redirects to the original app and 404's "/ui/apps/my.coe.cicd.observability/PipelineExecution?id= .... etc. But since it is now a "Community App" the ID for the app has changed, but it seems the code is still hard coded to point to the old app ID route.

This is currently happening in demo.apps even.

404 This application doesn't exist.

https://demo.apps.dynatrace.com/ui/apps/my.coe.cicd.observability/PipelineExecution?id=1789273263002&start=2026-09-13T04%3A06%3A03.094000000Z&end=2026-09-13T04%3A07%3A18.313000000Z&duration=0.75219

update the URL to:

https://demo.apps.dynatrace.com/ui/apps/community.cicd.observability/PipelineExecution?id=1789273263002&start=2026-09-13T04%3A06%3A03.094000000Z&end=2026-09-13T04%3A07%3A18.313000000Z&duration=0.75219

and it works.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'Explorer tab'
2. Click on '3 dots on any pipeline'
3. Click Pipeline Execution Flamegraph
4. See error --> 404 This application doesn't exist.

**Expected behavior**
Open to the flamegraph. If you swap the URL to the actual app ID "community.cicd.observability" the flamegraph shows up so its really just the redirect URL is wrong.

**Screenshots**

Image

**Additional context**
Add any other context about the problem here.

Contributor guide

Open the contributing guide

Research direction

Start from the Explorer tab's Pipeline Execution Flamegraph action and trace the redirect URL it generates. Replace the old app ID with community.cicd.observability, then reproduce the reported steps and confirm the flamegraph opens instead of returning a 404.

Written by the indexing model from the issue text.

Assessment

Domain
devops, observability
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
74/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.