We can already monitor available disk space and check individual BizTalk database sizes in Operations. What is missing is a way to understand how those sizes change over time.

A database server can lose a significant amount of free space before the cause becomes obvious. By the time Operations reports the issue, we may only see the result rather than which database started the problem.

A historical view in Analytics or Reporting, such as a 30-day line chart or stacked bar chart, would make this much easier to investigate. It would help us compare database growth, identify unusual changes, and see whether a particular database is responsible for the increasing storage usage.

This would also be useful for capacity planning. Instead of waiting for disk space to become critical, we could spot growth trends earlier and decide whether cleanup, retention changes, or additional storage are needed.

The goal is not just to monitor how much space is available, but to understand what is consuming it and how that changes Crossy Road over time.