Archives of the TeradataForum

Message Posted: Mon, 15 Dec 2003 @ 20:58:34 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Hi

i have created an application on our intranet for teradata "realtime" monitoring:

metholology:

.NET applicatione for data aquisition using pmapi and oledb. ASP.NET web pages as user interface.

its used by DBAs and buisness users to get there overview of our DWH in "realtime", 30 secs to 1 min delay

Node, AMP, PE and session summary information every 1 min as charts.

some examples:

Node CPU usage:

for each node or summary for all nodes: System CPU, User CPU, Wait IO Node Disk usage

for each node or summary for all nodes: Disk Reads, Disk Writes, Disk Use SpoolSpace usage, CPU usage, IO usage for users or resource partions

Session overview information

count of active, idle, blocked, aborting ... Sessions on the system

these charts are refreshed every minute and show 3 typical histroy time intervalls online: last 4 hours, last 24 hours and last 48 hours. its nice to see in the morning what was going on during the night, weekend ...

the total history i keeped for 1 year and the charts can be reproduced in any time intervall you like, from 10 mins to 1 month with any possible start timestamp.

Session Detail Information,

nearly the same information as the pmon detail page for all non idle sql sessions as html table, one table for all sessions, with some additional informations or grafical informations like:

SQL Statement and Explain for all Sessions with additional information like Explain Step runtime, syntax highlightning and ...

Skew Chart for IO and CPU, LHR for Request, LHR for last 10 mins and ...

spoolspace chart, parallel efficiency chart and ...

additional table with blocking information, who is blocked by whom with possibilty to kill the guilty sessions, only for the DBAs of course ;-)

this webpage is refreshed every 30 secs, different user groups gets different granularity. for example our developers can easly see whats going on on our development machine nearly in "realtime" during there development but only for there own queries, or our dba can find out easly the guilty query / end user which is heavly loading our production system. the DBAs can see all available informations.

other things like

tablespace usage with trend chart,

heartbeats,

batch job information like start/stop time, status

are also available inside this intranet application.

	<Prev	Next>		<<First	<Prev	Next>	Last>>