microsoft / microsoft/finops-toolkit

[Hubs] Troubleshooting tool

Open
#1,391 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

OKR: 1.2 Reliability Tool: FinOps hubs Tool: PowerShell Type: Feature 💎
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

📝 Scenario

As a FinOps hub admin, I need to identify and resolve common issues in order to get my hub in a healthy state

💎 Solution

Create a troublehsooting tool that can identify problems and recommend solutions to those problems.

This may require creating other commands to test various aspects of the account, like validating private endpoints or access to storage.

### Ideas to consider
- [ ] Give instructions for how to download/configure Power BI reports with specific values
- [ ] Does the storage account have a firewall enabled?
- [ ] Include networking details + validate connectivity + recommend fixes for connectivity issues
- [ ] Implement all processes and checks from the troubleshooting guide
- [ ] Suggest what team should help with issues for Microsoft Support routing
- [ ] Confirm the event hub resource provider is registered
- [ ] Confirm the triggers have started in ADF
- [ ] Collect any errors from ADF logs
- [ ] Look up errors in ADX (especially ingestion failures)
- [ ] Look up template deployment errors
- [ ] Look up errors against documentation to determine if there are known resolution steps
- [ ] Are there any failed pipeline runs in the last 7 days that were not re-run?
- [ ] Consider adding SLA metrics, like perf and reliability

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.

Contributor guide

Open the contributing guide

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

No files, tests, or command entry points are named. Start by reading the referenced troubleshooting guide and comparing it with the listed checks across storage, networking, ADF, ADX, Event Hubs, and template deployments; the scope and completion criteria need to be defined before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
cloud, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.