Dashboard not showing statistics.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- cloud, observability
Research direction
The issue names no files, tests, or entry points. Start by reproducing the deployed start\stop v2 dashboard behavior and checking how dashboard statistics are expected to be populated. Done means the dashboard displays data while VM start/stop continues to work.
Written by the indexing model from the issue text.
Description
I have deployed the start\stop v2 solution a week ago and was reviewing the dashboard information. While the functions for starting\stopping VM’s are working correctly the dashboard returns no data.
Any hints of what can be happening?
Thank you in advance.
- Dominant language
- No language data
- Stars
- 58
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from microsoft/startstopv2-deployments
-
.NET version supportOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/startstopv2-deployments#155 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
microsoft/startstopv2-deployments#149 · 2 comments ·
All issues in microsoft/startstopv2-deployments
Similar issues
-
Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/product-integrator-mi#5061 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
Team: SCM
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/BCApps#12012 · 1 comment ·
Maintainers usually reply within 1 day
-
developer-experience documentation high
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anchapin/staging-studio#1117 ·
Maintainers usually reply within 1 day