The barriers are things like integration effort, carrying cost (keeping up with updates and the toil to keep the tool going), poor signal / noise ratio and su

The barriers are things like integration effort, carrying cost (keeping up with updates and the toil to keep the tool going), poor signal / noise ratio and subsequent triage and debugging effort, additional feedback to dev team (valuable!) but often with no additional time to address it (demoralising), driving workflow changes for whole dev team (not just 1 or 2 enthusiasts) is hard, training & learning costs, and finally an inertia effect - the business shipped successful product without $tool in the past (otherwise there would likely be no money to buy it) and this is a trivial proof that $tool is not "essential".