Issue with Dashboard and logs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- observability
Research direction
Start by reproducing the dashboard's missing chart data and compare it with the events present in the logs. Investigate the logging configuration referenced in the issue; the work is done when the necessary events are logged and represented in the dashboard.
Written by the indexing model from the issue text.
Description
Hi there,
does anyone experience issues with the dashboard? The information in the charts are missing a lot of event data. When looking into the problem, it seems that not all events are logged. Are there any specific configurations that need to be done to generate the necessary log information?
thx, Chris
- 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 · 2 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
-
agent-ready area:platform bug criticality:p3 rust triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
registrystack/registry-stack#1583 · 1 comment ·
Maintainers usually reply within 1 day
-
factory-active factory-automatic task-bug-reproduction-success task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
vercel/ai#21528 · 3 comments ·
Maintainers usually reply within 1 day
-
difficulty/starter 🚀 good first issue kind/bug platform/all project/core-tools 🛠️ triage/untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
unoplatform/uno#24757 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JanusGraph/janusgraph#4988 ·
Maintainers usually reply within 1 day
-
examples(basic-tracer-node): SimpleSpanProcessor fails silently due to outdated constructor callOpenbug triage
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
open-telemetry/opentelemetry-js#7121 ·
Maintainers usually reply within 1 day