microsoft / microsoft/modernize-cli

feat: aggregated assessment report app assessment and cost estimation inconsistent

Open
#33 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
20
Forks
7
PR merge metrics
No merged PRs in 30d

Description

As an engineer I would like to get a complete and consistent assessment of my applications, combined with a realistic cost estimation and Azure SKU guidance.

As shown below, while the JavaScript app could technically not being assessed completely the guidance is rehosting to AKS, and the Java app should be moved to Azure App Service. Both apps are insurance backend services. My expectation would have been bringing both either to AKS or ACA - from an architecture design perspective the guidance shown here it does not make much sense and I have no information available why these SKUs have been chosen.

On the application assessment tab is also not the target SKU of the node app displayed, but on the cost estimate tab.

Test repository used: https://github.com/jkordick/agentcon-25-swe-agents
Image
Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the inconsistency using the linked agentcon-25-swe-agents test repository. Compare the application assessment and cost estimate tabs for the JavaScript and Java services, then trace how hosting recommendations and Azure SKUs are selected. Done means both views provide consistent guidance and explain the selected target SKUs.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, kubernetes
Domain
backend-api-design, cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.