Technology data
You can generate massive amounts of data by turning logging on. Yet, you have to work under the assumption that if no red lights are on, things must be OK. The amount of data under your control is irrelevant if it can't be combined into useful configurations.
If network latency is increasing at a given node, do you wait until an alarm goes off? As a DBA, if I/O metrics look good but customer reports of long wait times are increasing, when do you take action?
What are the relationships between application, DBMS, server, OS, disk drive type or manufacturer, network facilities and usage patterns that should cause an enterprise red light to come on even if each component seems to be functioning within parameters?What is an atypical usage pattern for a domain account that could indicate a compromised password? What does a typical usage pattern look like for each account?
Everyone today understands the negative impact of silos of information. Technology infrastructure seems to be a haven for silos nonetheless. Because the electronics are operating in a different kind of "real time" than the people processes in the company, community and communication have to be treated differently as well. Here is one area where we will have to put technology to work to solve the problem. In order to do that, though, we are going to have to create a human community to define the kinds of relationships that we need between different technologies.
It may be difficult for a lover of technology to concede the need to form relationships with people, but the path to the answers we need lies through people.
The best information for the best decision.