I see lots of problems when tools are confined to specific teams, as opposed to being open and shared by engineers and administrators across disciplines. Orion NPM is a good example, since many people still view it as a "network" tool, even though its ability to monitor and alert on servers is well established. Shops that isolate tools to teams spend much more on software and implementation than they should, and now have an integration problem to solve to get two or more monitoring packages working with their help desk solution.
The opposite problem is when an organizational policy mandates that a single monitoring tool be used for EVERYTHING. It may be that the organization has a heavy investment in a big product, and wants to get the most out of that investment. The problem here is that no one tool can monitor everything, and forcing the solution onto the problem is not an ideal way to run a business.