@tom Sorry... off to the coffee machine...
Posts made by Rob Fitzpatrick
It seems the dashboard layout changed recently.
I am looking at "Main Dashboard" for a monitored database. I have the following panes:
- Latest Status (13 panels)
- a new unlabelled one that says "CPU: Unknown • Memory: Unknown • OS: Unknown"
- General info (3 panels)
- Database I/O (3 panels)
- Transactions & Locks (3 panels)
- Record activity (3 panels)
- Network metrics (3 panels)
- Async Writers Statistics (3 panels)
There used to be panes for BI and AI info. Have they been relocated? Will they be returning?
SQL Servers are double-counted in 3.141x
case _Connect-type: ... when "sqsv" then tt_Dashboard.con_sqlServ = tt_Dashboard.con_sqlServ + 1. ... end. //case if _Connect-type begins "SQSV" then tt_Dashboard.con_SQLServ = tt_Dashboard.con_SQLServ + 1.
This may also be in previous versions; I haven't checked.
RE: Alert re lkHWM near lkTableSize
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.
Good to know, thanks.
Alert re lkHWM near lkTableSize
Maybe this belongs in "Roadmap" rather than "Using", but anyway...
Looking at alert.cfg:
# # Metric Type Compare Target Sensitivity Notify Message Action # ====== ==== ======= ====== =========== ====== ==================== ======================= # LogRd num > 100000 3:5 Always "Hit Ratio &1 &2 &3" alert-message,alert-log # # Metric The ui-det name of the field being monitored. # # Type Data type -- char or num (string or numeric). # # Compare Operator -- >, <, =, <>, <=, >= # # Target The threshold value of the metric to be tested.
Since it isn't stated explicitly, does "Target" have to be a constant? Could it be another metric of the same data type as "Metric"? Or an expression on constants or metrics (e.g. lkHWM * 0.8)?
Use case: let's say I want to configure an alert to fire when the lock HWM is getting close to -L, and have it work regardless of the value of -L, which could possibly vary over time or from one DB to another. Is that possible? Or do I just need to decide which number (say, 7000) I care about and configure it to alert when lkHWM > 7000?
Food for thought: the alerting mechanism would become more powerful if the target values could be dynamic in some way. Maybe passed to the back end via the API.
RE: Report inactive indexes
For reference, the non-essential audit indexes (which are often purposely deactivated, except in audit archive DBs):
RE: Release 3.141 is drawing nigh!
Possible bug: "%" must be invoked twice to have effect
I start pt3.141x against a DB, and Sample Type is "Rate/Interval" (as expected). When I hit "%" and select "Raw/Summary" and F1, the stats don't change. It says "RAW Summary" at top left but the stats are still interval rates. Hitting spacebar to refresh doesn't help. When I hit "%" and select "Raw/Summary" and F1 a second time, the raw stats appear as expected.
It appears this is the case for any changes in Sample Type. Changing back from "Raw/Summary" to "Rate/Interval" has the same issue, as does changing to "Cumulative/Summary".