| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.tools -> Re: Oracle metrics - any useful ideas on what to track?
David,
The phrase you are looking for, I believe, is 'SLA' (Service Level
Agreement).
In big organisations, these are (or should be) *always* defined at some
point during application design and development. If you have an on-line
query type app, it's very often query response time (either just a mean, or
more usually a 95% confidence interval or something like that) that should
be measured.
This can be measured in testing, benchmarking and in production. It should
be measured and records should be kept. How else are you going to know if
the service is acceptable?
The other thing to measure (which should also be included in SLAs) is what
someone else here called 'uptime' I think. Just as important as how the
system performs when it's up, is what percentage of the time it is up
(excuse awkward sentence construction :-)).
The purpose of the more technical data gathering, eg bstat/estat, event tracing, file system usage analysis etc. is: *Diagnose the cause of problems leading to breaking of SLAs *Prediction of system performance when workload increases.
Admittedly it all depends on the exact nature of the audit.
HTH
Adam
David Van Zandt <dvanzandt_at_iquest.net> wrote in message
news:eyH_6.14$q34.18599_at_news1.iquest.net...
> It's audit time in my division and pretty graphs are the sizzle to the
> steak, so to speak. Between IOUG, OEM, and STAT I have a decent
repository
> of trends documented. Unfortunately, my Pooh brain is stumped on what
> historical data may be seen as useful -- the purpose, heh, is to document
> the degree of fulfillment to our customer expectations. Customers, in
> general, don't give a flip about ratios or table sizes.
>
> Any useful ideas gratefully welcomed. Thanks all.
>
> Dave Van Zandt
> Senior DBA, Alcoa
>
>
 |
 |