I depends 😉
$$$ caused me to have to build my own inventory solution, providing simple history information for instance settings, databases, tables, indexes and volumes.
And a good lesson it has been. Learning and detecting where and how DMO and SMO can help out in a performant way ... or not.
For the great solutions that are available on the market, $$$ and licensing types are the big setback issues.
Another huge problem is the add-ons to as well your target server(s) as well as your user databases.
Especially if you want to remove the product afterward, in many cases leaving unused stuff on the os or in your db.
One of the "problems" with many state of the art packaged solutions, is generalisation. There seems to be no simple way of defining high priority servers vs low priority using e.g. profiles and exception rules.
This would come to studying your products xml config, ... in detail or accepting the vast amount of alerts being generated and overlooking the single one you needed.
And yes, in many cases, the HW you would need to collect and process your needed data would be way to expensive (on top of the product ! ) to get your total projects budget approved, because for the product, you can start small and buy extra licenses when needed, but your infrastructure must be in place as of day 1 !
In many cases, there is a different product to do your firefighting vs doing your evolution analysis. No problem with that, but many times, these products aren't using the same set of data or can't even share the provided data.
Accountants that manage your purse, aren't interested in the great stuff you see when evaluating a product.