<< | [up] | >> |
dim_STAT User's Guide. by Dimitri |
Administration |
Several administration points were already covered in previous sections. Let's speak about some other, more oriented on day to day management...
Active/Finished Collect |
Each STAT-collect may be only in 2 states:
- Active
- FinishedThe collector's "state value" is keeping all the time in the database. So, any state changement action via Web interface are only updating a corresponding database record, that's all. Each collector itself time to time check its record for state changement, and if so doing corresponding action...
Since v.7.0, any finished collect may be restarted again at any time.
Active: collector brings data from demanded server via STAT-service, and while service is up - continue data inserting into your database; once STAT-service is down, trying to re-connect every 20sec.
Finished: collect is stopped as well all its stat commands (normally), and no more data inserted into the database...
Delete/Recycle Collects |
Finished collects may be completely removed from the database, or recycled - you may remove, for example, all data previously collected to the last N days. Actually only manual recycle is possible.Note: any delete operation frees space in database index/data files, but not reduces file sizes itself! Freed space will be simply reused for next collects.
Database deleting was covered previously in "MySQL Admin Tips"...
Since v.8.1 Auto-Recycle module is integrated into dim_STAT. Well, it's still need to be run by cron or other execution planner, but at least configured once it gives you a simple way to recycle your collected data automatically without any human or manual action...First of all in your '/apps/ADMIN' directory you may find 'dim_STAT-Recycle' command:
# /apps/ADMIN/dim_STAT-Recycle Usage: dim_STAT-Recycle -Days N [-Base DBname] [-ID CollectID] -Days N -- keep data collected during last N days -Base DBname -- database name(s) (def: Default) -ID CollectID -- collect id(s) (ex: id1,id2,id3) (def: All active collects)So, to recycle every 24 hours and keep in your non-stop database 'Prod' only data collected within last 3 weeks all you need is just to add into crontab on your dim_STAT server:
0 0 * * * dim /apps/ADMIN/dim_STAT-Recycle -Days 21 -Base ProdNOTE: Days delay is pure calendar! Means, recycle will delete all your data from last collected day to N calendar days back - independently of possible inactivity holes in collected data!
Export/Import collects |
Collect Export and Import is an easy way to save/copy/restore small amount of data in compressed form. In case you need to copy a big amount of data - copy the whole database and don't loose your time! (get a look on "MySQL Admin Tips")
Modify Collect parameters |
** You should be VERY CAREFUL with these actions! **Changing Title and Hostname are just a part of decoration :))
Changing Collect-ID, as global operation, will lock during modifications all corresponding tables!
Changing Time Interval have sense only with wrongly loaded data from output files, otherwise be aware you're changing your time scale and totally loosing synchronization with real world events...
Changing Start Time have sense when you want to compare similar workloads collected on different elapses of time. You may bring them to the same time scale and analyze via Milti-Host mode. However, if you have any LOG messages corresponding to the same collect - don't forget to move them in time also to keep timestamp synchronization...
LOG Messages operations |
In case there are too much messages, or you want to share them with other collects, or you want to move them slitely in time, etc. - you can do all that and much more via "LOG Messages Admin".
<< | [up] | >> |