Counters

1. JVM COUNTERS:
Process CPU Time:
Indicating the total amount of CPU time consumed by JVM.
Garbage Collector time (Garbage Collection Time):
Indicates the cumulative time spent on garbage collection and total number of innovations (invokes).
Current Heap Size:
Indicates the no of kilobytes (Kb) occupied by objects.
Free memory:
Available memory in the heap.
Garbage collector interval Time: time difference between garbage collection cause.

2. CLR (Common Library Runtime) Counters:
 Exception through per second: Indicating number of managed code exceptions
thrown per second.
 Timing GC: Time spent on garbage collection.
 .net CLR memory heap size:
 .net CLR total committed bytes
 .net CLR large object heap size

3. WEB SERVER COUNTERS:

Apache:
 CPU load: Percentage of the CPU consumed by apache server.
 Request per second: The total number of request per second served by apache.
 Bytes per second(throughput)
 Busy workers: Number of active threads serving the request.
 Ideal workers: Number of inactive threads in the apache.

IIS SERVER (INTERNET INFORMATION SERVICES):

NOTE: IIS is a web app server for .Net based application.

 Bytes sent per second.
 Bytes received for second.
 Current connections.
 Request per second disconnection ratio.
 Number of request queued.
 Number of requests rejected.
Anonymous Users:
Indicating anonymous http connections in the particular tab.


4. APPLICATION SERVER COUNTERS:

Web logic server:
 Execute the thread total count: Indicating the total number of threads assigned to
queue.
 Pending request current count: Indicates number of pending request in queue
 Queue length: Number of request in the priority queue.
 Throughput: number bytes received per second.
 Exception count: It should not cross 20.
 Connections current count:
 Transactions roll back total counts: it should not cross 5.

WEBSPHERE (IBM WAS) COUNTERS:
 Concurrent request: Number of requests are concurrently processed.
 Service time: Response time for a servlet request.
 Active count: Number of active threads in the system.
 Connection pool size: Number of threads in the pool.

5. Network Counters:
 Connection established: indicating connections success ratio.
 Connections failure: Percentage of connections failure.
 Through put:
 Network latency (delay):
 Pocket loss:

6. Disk Counters:
Disk read per second:
Disk writes per second: rate of write operations on the disk.
Average disk queue length: Number of read and write request that were queued for selected disk during the sample interval.
Disk time: percentage of the elapsed time that the selected disk was busy with serving read and write request.

Note:
Average disk queue length should not cross to for every disk.
Split I/O‘s Second: Measures the rate of I/O split due to file fragmentation.
Free space: Display the percentage of total available space.

7. Database Counters:
 We can monitor oracle 10g versions using DB stats reports above 10g.
 AWR reports.

Note:
Even DBA can generates the DB trace (or) oracle trace report to identify dead locks and full table scan.

Oracle counters (for all java based applications):
 Buffer hit ratio
 Full table scan
 Indexing
 DB time
 DB CPU time
 Hard parses and soft parses
 Top 5 time taken events(in a particular durations)
 Physical read
 Physical writes
 High CPU utilized query’s
 High memory utilized query’s
 High I/O’s utilized query’s

SQL Server Counters (.NET based applications):
Using sql profile we can monitor DB activities.
Navigations:
 Open SQL server
 Choose new option
 Choose create new profile.
Counters:
Buffer cached hit ratio.
Transactions for second.
Log cached hit ratio.
Page read per second.
Page writes per second.

SAP HANA Counters:
Using SAP HANA studio we can monitor SAP HANA.
SAP HANA built on column and row based technology.But purely work on column based.