using "top" linux semi-permanent instrumentation
i'm perplexing best proceed 'top' semi-permanent orchestration growth box controlling embedded linux. (the orchestration private final-test prolongation releases.)
my initial pass simply supplement init.d:
top -b -d 15 >/tmp/toploop.out &
this runs tip "batch" mode each 15 seconds. let's assume /tmp excess space
questions:
- is 15 seconds good value select general-purpose monitoring?
- other hoop space, extremely perturbing state system?
- what (perhaps better) collection used this?
Comments
Post a Comment