The Alerts Feed and Critical Alerts panes each have three columns of information. They don't have column headers but let's call them Time of Day, Resource Name, and Alert Details. When you hover over the alert, a "window" pops up with additional details about the alert.

The issue is that the right edge of this window is aligned always to the left of the Alert Details column. So in the case where the pane is either on the left side of the dashboard or it is maximized, about half of the pop-up window is cut off so its content can't be read. This makes the ability to drag these panes to the left side of the dashboard, or to maximize them, useless.

Example:

In cases where the pop-up window would otherwise extend past the left side of the display, it would be preferable its alignment was changed to align its left side with the left side of the display, rather than aligning its right side with the Alert Details column.

I'm looking at alerts in the Alerts Feed and their accompanying tooltips or pop-ups or whatever those boxes are called that you see when you hover over an alert.

One alert was like "tblRd Table reads/sec x > y". The pop-up has some header info, followed by a table of users by logical reads and tables of table and index CRUD. Some of the table CRUD line items end with "***", to the right of the "Churn" column.

In my browser (Firefox), these pop-up boxes are very finicky. It is sometimes difficult to make them appear by hovering over the alert, and when they do they sometimes disappear after some period that I can't discern.

Questions:

• What is the meaning of the three asterisks beside a table record?
• Are there any ProTop UI configuration settings that govern the behaviour of these pop-up boxes?

I was looking through ProTop and was somewhat surprised to find that it doesn't seem to report inactive indexes anywhere. Just wondering whether that has been considered as a feature, e.g. as a counter (# of inactive indexes) in the configuration panel.

Given the performance problems that an inactive index could cause, it would be useful to alert if this number was non-zero (perhaps excluding audit indexes).

@tom said in OE 12 support:

Lastly, I also (sneakily) patched the pt3.14 release a week or so ago. If your "as of" date on that is in May rather than March then you should also have the oe12 changes (but not the "4" hotkey).

That explains it, I got the error from the original March version.

3.14 (without the .1592653589793 patch...)

@tom said in Configure the User Information Viewer:

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.

┌────────────────────────────── Error ──────────────────────────────┐
│            Unknown or ambiguous table _startup. (725)             │
│ ** /opt/protop/lib/vstlib.p Could not understand line 880. (196)  │
│                                                                   │
│ ───────────────────────────────────────────────────────────────── │
│                            <OK> <Help>                            │
└───────────────────────────────────────────────────────────────────┘

Any update on OE 12.x support for PT?

I used to be able to turn off the "Session 4GL Call Stack" and "User's Other Sessions" browses with the "3" and "4" hotkeys respectively.

Did those assignments go away or get reassigned? I'm using 3.14.

@tom said in Happy pi day - pt3.14 has been released!:

Go to your usual website and grab a download!

Or upgrade from the command line: $PROTOP/bin/pt3upd.sh pt3.14

@tom said in Happy pi day - pt3.14 has been released!:

@rob-fitzpatrick I like that you said “if”

Well, there's a first time for everything...