Regarding the specific alert: there is a lkTblPct field which I use for a similar purpose. Rather than the HWM it reflects the locks in use at that moment. In some ways that is better -- the HWM sticks around until you restart and if something went bump in the night is going to keep alerting once you hit the threshold.
The -tablerangesize or -indexrangesize parameters are not set to cover the active tables & indexes. The ChUI "T" command will show you what values are recommended and create a sample .pf file for you in the ProTop temp directory. Unfortunately you cannot change these values online. A db restart will be needed.
The activity on the tables and indexes does not meet the threshold criteria. You can review the thresholds on the portal "Resource" screen. For development and test environments you probably want very low values. For Production you want higher values -- a chart with 2,000 objects on it will be unusable (that is why we have a minimum activity threshold).
You should also verify that etc/pt3agent*.cfg has the TableActivity and IndexActivity data collectors enabled. If they are missing from ptInitDC then that data is not being sent to the portal.
I'm thinking that the statement cache should automatically appear or disappear based on whether or not it is enabled for a particular client.
That's reasonable. Though I'd still like to be able to turn the individual browses on or off. 😉
It would also be nice to have the act of turning off User Information Viewer revert to a view that is more useful, as opposed to just removing the header section. E.g. if the act of going into it cached the current list of displays (e.g. d, t, i, u), so they could be restored when u is pressed again. Food for thought.