Command
Finance
Command
/hubs-health-check
Check deployed hub version against latest stable and dev releases and validate data freshness.
Install
> /plugin marketplace add microsoft/finops-toolkitHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/hubs-health-check
Context preview
What this command does when you run it.
Check deployed hub version against latest stable and dev releases and validate data freshness.
Command definition
hubs-health-check.mddescription: Check deployed hub version against latest stable and dev releases and validate data freshness.
disable-model-invocation: true
FinOps hubs health check
Step 1: Check the latest released FinOps hub version
Get the content from this file to determine the latest stable version of FinOps hubs: `https://raw.githubusercontent.com/microsoft/finops-toolkit/refs/heads/main/src/templates/finops-hub/modules/ftkver.txt`.
Get the content from this file to determine the latest development version of FinOps hubs: `https://raw.githubusercontent.com/microsoft/finops-toolkit/refs/heads/dev/src/templates/finops-hub/modules/ftkver.txt`.
FinOps hubs use semantic versioning (SemVer) format for version numbers, which is `major.minor`, `major.minor.patch`, or `major.minor-prerelease`. If the version number has `-dev` at the end of it, that means it's a development version.
Compare the version of the current FinOps hub instance with the latest stable version of FinOps hubs. If it's the same version as stable, tell the user they are using the latest released version and skip to the next step.
If the FinOps hub version is the same as the development version, tell the user they are using the development version and they should monitor the repository to ensure it's updated with the latest changes, then skip to the next step.
If the FinOps hub version is older than the development version and matches or is older than the latest stable version, tell the user they are using an older development version and should update to the latest stable release or development version. Mention their version number and the latest stable and development version numbers. Give them this link to deploy the latest stable version depending on their Azure cloud environment:
- For the Azure public, commercial cloud, use https://aka.ms/finops/hubs/deploy
- For the Azure Government cloud, use https://aka.ms/finops/hubs/deploy/gov
- For the Azure China cloud, use https://aka.ms/finops/hubs/deploy/china
Step 2: Check the latest data refresh/update date
If the last data refresh/update date is less than 24 hours ago, skip this step.
If the last data refresh/update date is more than 24 hours ago, inform the user that the data may be stale and they should check the Microsoft Cost Management exports and Azure Data Factory data ingestion pipelines to ensure they are running without errors.
Give them a link to Microsoft Cost Management to check the exports: https://portal.azure.com/#view/Microsoft_Azure_CostManagement/Menu/~/exports
Give them a link to the Azure Data Factory portal to check data ingestion pipelines: https://adf.azure.com/monitoring/pipelineruns
Tell the user you can help them troubleshoot any issues with [common errors](https://learn.microsoft.com/cloud-computing/finops/toolkit/help/errors) and the [troubleshooting guide](https://learn.microsoft.com/cloud-computing/finops/toolkit/help/troubleshooting).
Read more
description: Check deployed hub version against latest stable and dev releases and validate data freshness. disable-model-invocation: true
FinOps hubs health check
Step 1: Check the latest released FinOps hub version
Get the content from this file to determine the latest stable version of FinOps hubs: `https://raw.githubusercontent.com/microsoft/finops-toolkit/refs/heads/main/src/templates/finops-hub/modules/ftkver.txt`.
Get the content from this file to determine the latest development version of FinOps hubs: `https://raw.githubusercontent.com/microsoft/finops-toolkit/refs/heads/dev/src/templates/finops-hub/modules/ftkver.txt`.
FinOps hubs use semantic versioning (SemVer) format for version numbers, which is `major.minor`, `major.minor.patch`, or `major.minor-prerelease`. If the version number has `-dev` at the end of it, that means it's a development version.
Compare the version of the current FinOps hub instance with the latest stable version of FinOps hubs. If it's the same version as stable, tell the user they are using the latest released version and skip to the next step.
If the FinOps hub version is the same as the development version, tell the user they are using the development version and they should monitor the repository to ensure it's updated with the latest changes, then skip to the next step.
If the FinOps hub version is older than the development version and matches or is older than the latest stable version, tell the user they are using an older development version and should update to the latest stable release or development version. Mention their version number and the latest stable and development version numbers. Give them this link to deploy the latest stable version depending on their Azure cloud environment:
- For the Azure public, commercial cloud, use https://aka.ms/finops/hubs/deploy
- For the Azure Government cloud, use https://aka.ms/finops/hubs/deploy/gov
- For the Azure China cloud, use https://aka.ms/finops/hubs/deploy/china
Step 2: Check the latest data refresh/update date
If the last data refresh/update date is less than 24 hours ago, skip this step.
If the last data refresh/update date is more than 24 hours ago, inform the user that the data may be stale and they should check the Microsoft Cost Management exports and Azure Data Factory data ingestion pipelines to ensure they are running without errors.
Give them a link to Microsoft Cost Management to check the exports: https://portal.azure.com/#view/Microsoft_Azure_CostManagement/Menu/~/exports
Give them a link to the Azure Data Factory portal to check data ingestion pipelines: https://adf.azure.com/monitoring/pipelineruns
Tell the user you can help them troubleshoot any issues with [common errors](https://learn.microsoft.com/cloud-computing/finops/toolkit/help/errors) and the [troubleshooting guide](https://learn.microsoft.com/cloud-computing/finops/toolkit/help/troubleshooting).
Ships withfinops-toolkit
Quick links: The FinOps toolkit is an open-source collection of customizable tools and resources to help you adopt and implement FinOps capabilities that automate and extend the Microsoft Cloud.
Get the whole plugin
Stats
613
Stars
259
Forks
Active
Maintenance
PowerShell
Language
MIT
License
2h ago
Last commit
3y ago
Created
4h ago
Added
Repo: microsoft/finops-toolkit
Other commands on finops-toolkit.
Command
Command
Command
hubs-connect
Discover FinOps hub instances via Azure Resource Graph, connect to a cluster, and save…
@microsoftView CommandCommand
mom-report
Autonomous month-over-month cost analysis with anomaly detection, forecasting, and actionable…
@microsoftView CommandCommand
ytd-report
Comprehensive fiscal year-to-date cost analysis with forecast through the organization's…
@microsoftView Command