Consider Adding Metrics to Track CPU and I/O Utilization for Better Performance Monitoring

Exposing the CPU and I/O utilization of methods that are likely to consume the most of those resources could provide insights into overall potential performance improvements to Accumulo. Further, exposing such metrics at the table level could help identify tables with inefficient schema, inefficient bulk import strategies, or have iterators or aggregators that are resource hogs.

This issue is to capture the methods or threads that are most likely to have high CPU or high I/O utilization.

The issue names no files, tests, or entry points. Begin by surveying Accumulo methods and threads that may have high CPU or I/O use, then determine where table-level visibility would belong. Done means the scope and metrics needed for method, thread, and table-level performance monitoring are defined.

Written by the indexing model from the issue text.