radius-project / radius-project/dashboard
Application Graph enhancements
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 18
- Forks
- 13
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 10
Description
Overview of feature request
Enhance the current application graph in Radius by incorporating links to other applications that it depends on. This feature will provide a comprehensive view of the entire application ecosystem, highlighting interdependencies and facilitating better management and troubleshooting.
Objectives
- Visualize the dependencies between the primary application and other interconnected applications.
- Improve understanding of the impact of changes or issues in one application on the entire system.
- Facilitate better planning, monitoring, and troubleshooting by providing a holistic view of the application network.
Key Features
- Dependency Mapping:
- Automatically detect and map dependencies between applications.
- Manual addition of dependencies for custom or legacy applications.
- Interactive Graph:
- Expandable and collapsible nodes to manage the complexity of the graph.
- Detailed information on each node, including application name, status, version
- Impact Analysis:
- Highlight potential impact areas when an application is down/not responding to health checks.
Benefits
- Enhanced Visibility: A clear and comprehensive view of application dependencies helps in understanding the complex web of interactions within the system.
- Proactive Management: Real-time updates and impact analysis enable proactive management of the application ecosystem, reducing downtime and improving reliability.
- Better Planning: Detailed dependency maps support better planning and coordination among development, operations, and management teams.
- Informed Decision Making: Accurate and up-to-date dependency information aids in making informed decisions regarding updates, maintenance, and troubleshooting.
Acceptance criteria
No response
Additional context
No response
Would you like to support us?
- Yes, I would like to support you
AB#12646
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the current application graph in the dashboard and clarifying how application dependencies are detected or entered. Define acceptance criteria for dependency mapping, expandable nodes, node details, and impact highlighting before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100