<< | [up] | >> |
dim_STAT User's Guide. by Dimitri |
Overview... |
dim_STAT is a tool for both high-level and detailed, monitoring and performance analysis of Solaris, Linux, and other UNIX systems.The main features of dim_STAT are:
- A web based user interface
- All collected data is saved in a database
- Multiple data views
- Interactive (Java) or static graphs (PNG)
- Real Time monitoring
- Multi-Host monitoring
- Post analyzing
- Statistics integration (Add-On)
- Professional reporting with automated features
- One-click STAT-Bookmarks
- etc.
All STAT data is collected from standard UNIX tools like vmstat, iostat, etc. (or some special ones, like psSTAT for monitoring users and processes activity) and saved in the MySQL database. Collected data is accessed via a web interface and can be presented in several manners (interactive or static graphs, text, HTML tables). Since v.8.1 there is also a way to collect data from other UNIX systems (HP/UX, AIX, MacOSX, etc.)
dim_STAT can be used for the on-line monitoring of one or several hosts at the same time. As well, data can be post loaded from output files of stat commands and analyzed in the same manner. At any time data collection from new stat commands can be added to the tool (via Add-On interface) to enlarge your view on application workloads, RDBMS, your personal STAT program, etc.
By default, dim_STAT interfaces with the following Solaris stats (SPARC and x86):
- vmstat
- mpstat
- iostat
- netstat
- psSTAT, ProcLOAD, UserLOAD (processes an users)
- ZoneLOAD, PoolLOAD, ProjLOAD, TaskLOAD (CPU/memory/etc. load per zone/pool/project/task (Solaris 10))
- netLOAD (extended network stats)
- UDPstats (UDP traffic)
- IOpatt (Solaris 10 I/O pattern via DTrace)
- vxstat (VxVM stats)
as well as the following Add-On extensions for both Solaris SPARC/x86 and/or Linux/x86:
- CoreSTAT (Solaris)
- MEMSTAT (Solaris)
- HAR v2 (Solaris CPU chip counters for SPARC and x64)
- jvmSTAT (Java VM GC Activity and Memory Usage stats)
- oraEXEC, oraIO, oraSLEEP, oraENQ, oraASMIO (Oracle activity stats)
- mysqlSTAT, mysqlLOAD, innodbSTAT, innodbMUTEX, innodbMETRICS (MySQL & InnoDB activity stats)
- pgsqlSTAT, pgsqlLOAD (PostgreSQL activity stats)
- LvmSTAT (Linux vmstat)
- LcpuSTAT (Linux mpstat)
- Lmpstat (Linux mpstat v2)
- LioSTAT (Linux iostat)
- LnetLOAD (Linux netLOAD)
- LpsSTAT (Linux psSTAT)
- LprcLOAD (Linux ProcLOAD)
- LusrLOAD (Linux UserLOAD)
- IObench (tool for I/O stress load)
- dbSTRESS (tool for database stress load)
- OSXiostat, OSXvmstat, OSXnetstat (experimental MacOSX support was added since v.9.0)
- and mostly any other program you want to add...
The CPU utilization of dim_STAT during collect is very low and even less than standard tools like top or perfbar.
General View |
Just to get an idea how dim_STAT works. Each machine you want to monitor in real-time should run a special STAT-service daemon (client). Via the web browser you start collectors to communicate with clients. All information collected gets saved in a database and may be analyzed as soon as the data is arriving or lateron. In general, all analysis, reporting or administration is done from the web browser. The web interface is developed and runs on WebX (my own tool) ...
<< | [up] | >> |