<< | [up] | >> |
dim_STAT User's Guide. by Dimitri |
FAQ |
Sizing of dim_STAT Instance... |
the problems is simple: there is no sizing rules at all...Disk space: it depends only on size of collected information... In Preferences page you can see used space by the current database and size of the biggest file: each file should be less 2GB in size, if it's not so - you have to create a new database!
CPU: during collect your CPU power is not used at all... However, once you start a query via Web interface you may access a really big amount of data! Your query became DSS (decisional) and may load 100% one CPU during execution... Normally query execution time is quite short, but directly depends on demanded amount of data.
Separated databases is fine when you may need different administrative tasks regarding to collected data. For example, it may be annoying if somebody loading a big amount of data on the same time while you're trying to analyze something... You will create additional locks and slow down work for others. MySQL (in used version) uses "table locking", so only one single writer on the same time, and write operation is exclusive (no read during it). If you use your own database you have less reasons to blame others :))
So, desktop running dim_STAT server may be heavy used as not used at all - it depends only on your activity...
I've started my collects but there is still nothing collected... |
First of all be sure:
- you've installed STAT-service package on this host and _started_ it!
- if you're collecting from Linux host: don't forget it generating different stat output and you need to activate linux Add-Ons first!If everything seems to be correct for you, chack the output of '/etc/STATsrv/log/access.log' file.
Syntax of text matching pattern |
Quite often in dim_STAT interface you may see an input text field to filter values or attributes matching specified pattern. By default they are filled with '*' (means all), but what kind of syntax it accepts?...Pattern by example:
- * - any character or none
- ? - any single character
- [amp] - single character and one from 'a', 'p', or 'm'
- [a-z] - any single character between 'a' and 'z' (both included)
- [^a-z] - any single character NOT between 'a' and 'z' (both included)
- !Pattern - apply NOT condition on the whole pattern
- Pattern || Pattern - apply OR condition between two patterns (or more)
- Pattern && Pattern - apply AND condition between two patterns (or more), has higher priority vs OR
Examples matching LOG messages:
- *Test??* - match all messages having TestNN in title
- *Test??* && *End* - match all TestNN messages containing End
- *Test??* && *End* || *Begin* - match all TestNN messages containing End or Begin
- !*Test??* && *End* || *Begin* - match any messages except TestNN and containing End or Begin
Will you upgrade to the newer MySQL version? |
But why?... :))
Should we change good old working horse just because it's old?... It works 10 years now and do exactly staff I need :)) and MyISAM is not working better in MySQL4 or MySQL5...What may be interesting, is to ship a parallel version with PostgreSQL! :))
But it'll be another story... Stay tuned :))
Full Working cycle Example |
TBD...
<< | [up] | >> |