<< | [up] | >> |
dim_STAT User's Guide. by Dimitri |
Overview... |
dim_STAT is a tool for general/detailed performance analyze and monitoring of Solaris and Linux systems.Main features are:
- Web based interface
- All collected data saved in SQL database
- Several proposed data views
- Interactive (Java) or static (PNG) graphs
- Real Time Monitoring
- Multi-Host monitoring
- Post analyzing
- New Statistics integration (Add-On)
- Professional Reporting with automated features
- One-Click STAT-Bookmarks
- etc.
All STAT data are collected from standard Solaris or Linux programs (vmstat, iostat, etc.) or some special (like psSTAT for users/processes activity) and saved in MySQL database. Collected data are accessed via Web interface and can be presented in several manner (interactive or static graphs, text, HTML tables). Since v.8.1 there is also a way to collect data from any other UNIX systems (HP/UX, AIX, etc.)
dim_STAT can be used for On-Line monitoring one or several hosts on the same time. As well, data may be easily post loaded from output files of stat commands and analyzed in the same manner. At any time collecting from new stat commands may be added to the tool (via Add-On interface) and enlarge your view on application workload, RDBMS, your personal STAT program, etc.
By default dim_STAT interfaces Solaris stats (SPARC ans x86):
- vmstat
- mpstat
- iostat
- netstat
- psSTAT, ProcLOAD, UserLOAD (processes an users)
- netLOAD (extended network stats)
- vxstat (VxVM stats)
as well add-on extentions for both Solaris and Linux/x86:
- MEMSTAT (Solaris)
- har2, har3 (Solaris SPARC only)
- jvmSTAT (Java VM GC Activity and Memory Usage stats)
- oraEXEC, oraIO, oraSLEEP, oraENQ (Oracle related stats)
- LvmSTAT (Linux vmstat)
- LcpuSTAT (Linux mpstat)
- LioSTAT (Linux iostat)
- LnetLOAD (Linux netLOAD)
- LpsSTAT (Linux psSTAT)
- LprcLOAD (Linux ProcLOAD)
- LusrLOAD (Linux UserLOAD)
- and any other program you want to add...
CPU usage of dim_STAT is very low and even less important than standard proctool, top, or perfbar. So given performance vision is more close to reality...
General View |
Just to get an idea about how it works. So, each machine you want to monitor in real-time should run a special STAT-service daemon (client). Via your prefered Web browser you start collectors to communicate with client(s). All collected information saved in database and may be analyzed later or on the same time as data arriving. Generally all analyzing/ reporting/ administration/ etc. tasks are doing via Web browser. All Web interface is developed an running on WebX (my own tool)...
<< | [up] | >> |