The "unknown" data comes from the osInfo data collector. You might need to add that to etc/pt3agent.cfg

AI, BI and APWs are combined now into a single "async writers" section.

Looks like it dates back to pt3.3n.

It is fixed now.

That's kind of dumb. Who the heck coded that?

That is an interesting idea. A more complex rules engine for the alert processing is something that I have been thinking about for a while. On the other hand there is a lot to be said for keeping it simple.

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. Whereas lkTblPct will only alert if something is actively causing a problem.

Nope. You're right -- that's a bit more difficult to calculate and it seems much less likely.

But I'll add it to the "think about it" list

The flakiness is being addressed in portal v4.

The "***" is indicating that there is an unusual relationship between table reads and the indexes for that table.

Speaking very broadly, usually you expect to see a single index that has more or less the same amount of activity as the table. If we see index reads at more than 1.5x table reads that is strange enough that we put a "***" there to draw your attention to it.

Portal v4 has a lot of enhancements to stuff like this. Real Soon Now.

Which reminds me of another needed alert "not having audit archive db"

I think I probably need more visuals. I'm not forming a picture in my head of what you are describing.