Jaa


Data ingestion report

The Data ingestion report provides details about the data that got ingested into your FinOps hub storage account.


Get started

The Get started page includes a basic introduction to the report with other links to learn more.

Screenshot of the Get started page that shows basic information and links to learn more.


Hubs

The Hubs page shows the cost of any FinOps hubs instances. Expand each instance to see the cost broken down by service (for example, Storage or Key Vault). Most organizations only have one hub instance. This page can be helpful in confirming how much your hub instance is costing you. And it helps confirm if there are other hub instances deployed within the organization, which could possibly be centralized.

This page includes the same KPIs as most pages within the Cost summary report:

  • Effective cost shows the effective cost for the period with reservation purchases amortized across the commitment term.
  • Total savings shows how much you're saving compared to list prices.

Screenshot of the Hubs page that shows the cost of FinOps hubs instances.


Exports

The Exports page shows which months were exported for which scopes, when the exports were run, and if any ingestion flows failed. Failures are shown in CSV files in the msexports container since that means they weren't fully ingested. To investigate why ingestion failed, you need to review the logs in Azure Data Factory. In general, as long as another ingestion was completed for that month, you're covered. Mid-month ingestion failures don't result in missing data since Cost Management re-exports the previous days' data in each export run. Exports are typically run up to the fifth day of the following month. If you see a date after the fifth day of the month, then that usually means someone ran a one-time export for the month.

Tip

If you only see one export run per month, you might have configured file overwriting. While this setting is important when using Power BI against raw data exports, it is not recommended for FinOps hubs because it removes the ability to monitor export runs over time (since files are deleted).

Screenshot of the Exports page that shows detailed information about exports.


Ingestion

The Ingestion page shows which months have been ingested and are available for querying in Power BI and other client apps. The FinOps hubs ingestion process doesn't create new files every day, so you might only see one to two files. The number of files gets determined by Cost Management when generating the initial partitioned CSV files.

Similar to exports that are run until the fifth day of the following month, you typically see ingested months being updated until the fifth day of the following month. If you see a date later than the fifth day of the month, it's often due to a one-time export run.

If you notice exports from before ingested months, it typically means older data was removed from the ingestion container but the export metadata wasn't removed from msexports. You can safely remove files in msexports at any time. They're only useful for monitoring export runs.

Screenshot of the Ingestion page that shows the months of ingestion data.


Ingestion errors

The Ingestion errors page summarizes potential issues that were identified after reviewing data in hub storage. For troubleshooting details about each error, see Troubleshooting Power BI reports.

Screenshot of the Ingestion errors page that shows a summary of potential problems.


Looking for more?

We'd love to hear about any reports, charts, or general reporting questions you're looking to answer. Create a new issue with the details that you'd like to see either included in existing or new reports.


Related FinOps capabilities:

Related products:

Related solutions: