System Related Monitors

Prepare Monitor Profile

  • Decide monitor list for the servers.
  • Create monitor profile on the basis of program name.

Recommendations: There are two ways to create monitor profiles.

  1. It is preferred that user create the mprof on the basis of monitor name. For Example: For MPstat monitor, mprof having all the Mpstat monitor for all the servers.
  1. But, the user can also create the mprof on the basis of the server. For Example: mprof having all the monitors for that particular server

Configuring the Weblogic (App Server) Monitor

User needs to add following monitors for Weblogic Server Environment:

  • First, configure all the monitors related to:
    • System Monitors
    • Process Monitors
    • Log Monitors
  • Then, configure all the monitors related to Weblogic server that are specified in the list.

Adding System Related Standard Monitors

User needs to follow the below mentioned steps for adding system related standard monitors:

  1. Login to NetStorm.
  2. Go to Monitors section on the left pane and Monitors menu item. The Monitor Group Management window is displayed.

50

  1. Click the Add button. The Add Monitor Group – New Profile window is displayed.
  2. Select the Topology name, enter group name and its description. Click the Save button.

51

  1. Click the Standard Monitor tab and click Add.

52

  1. The Add Standard Monitor window is displayed.

53

Provide the following details:

  • Tier name: The name of tier which the user created in topology
  • Server name: It shows only the server that is mapped with the selected Tier.
  • Standard Monitor Name: The monitor name that user wants to use.
  1. Click the OK button.

System Related Monitor List

System/Standard monitor list that is used for all type of servers:

SystemStatsExtended

It is extended version of system stats which provides information about processes, memory, paging, block IO, traps and CPU activity. It is supported for Linux, Solaris and AIX machines.

Steps to add: Follow the steps mentioned in “Adding System Related Standard Monitors”. Then add the Time interval in Second. By default, progress msec interval (10 sec) is considered for this interval.

IOStats

Report Central Processing Unit (CPU) statistics and input/output statistics for devices and partitions.

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time Interval in Second.

LsofStats

It provides count of different types of open files on Server.

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time interval in Second.

MPStat

It provides the statistics of all the processors available on targeted server.

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time Interval in Second.

NetworkDelay

It provides information about Network delay between two nodes. Source node is the node selected in the Server Name list box.

Steps to add: Firstly, follow the steps “Steps to add the Standard Monitor” then select the Network Delay Monitor and fill the parameters.

54

  • Destination Hostname/IP:  Hostname/IP of the Destination node. For example: DevNS
  • Packet Size (bytes): Packet size. For example: 1024 bytes
  • Packet Count: Number of packets. For example: 500 Packets
  • Enter Sample interval in secs: Sample interval in seconds.

TcpStatesCount

It provides information about number of TCP connections in different TCP states. User can use it on Linux, AIX and widows.

Steps to add: Firstly, follow the steps “Steps to add the Standard Monitor” then select the TcpStatesCount Monitor and fill the parameters.

55

TCP Monitors

  • Sample interval in Secs: Sample interval in seconds.

Get TCP states count for specified Local/Foreign Addresses

  • Include specified Local Address: Include Local Address in any format as host:port, host, :port or their any combination separated by comma(s).
  • Include specified Foreign Address: Include Foreign Address in any format as host:port, host, :port or their any combination separated by comma(s).
  • Exclude specified subsets for include addresses: Exclude Local/Foreign Address in any format as host:port, host, :port or their any combination separated by comma(s).

TcpStatsRate

It provides the information on rate value.

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time Interval in Second.

UpTime

It provides information about how long the system has been running, how many users are currently logged on and the system load averages for the past 1, 5, and 15 minutes.

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time interval in Second.

EthStat

It provides the information of all Ethernet interfaces available on the server. EthStat is preferred more than the EthThroughputStat.

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time interval in Second.

DeviceStats

It provides the information of all the Devices available on the server.

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time interval in Second.

EthThroughputStat

This monitor is same as the above EthStat monitor. It also provides the information of the throughput statistics.

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time interval in Second.

FileSystemStats

It provides the information of all the file system statistics available on the server.

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time interval in Second.

SockStats

It provides information about server socket statistics as used socket, total number of TCP socket used etc.

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time interval in Second.

ProcessCountByState

This is a monitor to count the processes in different states like:-

  • RUNNING
  • INTERRUPTABLE
  • STOPPED
  • ZOMBIE
  • RUNNABLE
  • IO
  • PAGING
  • DEAD

Steps to add: Follow the steps mentioned above in “Adding System Related Standard Monitors”. Then add the Time interval in Second.

Hadoop Monitor

To monitor following statistics of Apache Hadoop Server:

  • Name Node: NameNode HDFS Nodes, NameNode HDFS Capacity, NameNode Files, NameNode Fs Blocks.
  • Data Node: DataNode Read/Write, DataNode Health, DataNode Blocks, DataNode Block Operations.
  • Resource Manager: ResourceManager Nms.
  • Resource Manager Queue: ResourceManager Queue Status, ResourceManager Queue Applications, ResourceManager Queue Containers
  • Node Managers: NodeManager Containers, NodeManager Shuffle.

Steps to add: Follow the steps mentioned below:

Hadoop DataNode Monitors: Hadoop DataNode Stats Monitor.It monitors Total Bytes Read,Total Bytes Written, Blocks Read, Blocks Written, Blocks Replicated, Reads From Remote Client etc.

Steps to add the hadoop DataNode Monitors

  1. Standard Monitor Name: Select the HadoopData Node
  2. Instance Name: Instance name on which monitor should be configured.

56

HadoopDataNode Monitor Parameters:

  • Hostname: Host name where hadoop server is running
  • Port Number: Port number to connect to hadoop’s (name node, data node,yarn, job tracker, task tracker)
  • Username: User Name for hadoop
  • Password: Password for hadoop
  • Retry count: Retry when connection lost
  • Enter sample interval in secs: Specify refresh rate to get data (in seconds)

 3. Then click “OK”.

Hadoop NameNode Stats Monitor: It monitors Number of live data nodes, Number of dead data node, Deleted Files, Created Files, Pending Replication Blocks, Pending Deletion Blocks, Block Capacity etc.

Steps to add the hadoop NameNode Monitors:

  1. Standard Monitor Name: Select the HadoopName Node Monitor.
  2. Instance Name: Instance name on which monitor should be configured.

57

HadoopNameNode Monitor Parameters:

  • Hostname: Host name where hadoop server is running
  • Port Number: Port number to connect to hadoop’s (name node, data node, yarn, job tracker, task tracker)
  • Username: User Name for hadoop
  • Password: Password for hadoop
  • Retry count: Retry when connection lost
  • Enter sample interval in secs: Specify refresh rate to get data (in seconds)

3.  Then click “OK”.

Hadoop Node Manager Stats: It monitors Allocated GB,Available GB, Total Containers Completed, Total Conatiner Inited, Total Conatiner Running, Total Conatiner Killed.

Steps to add the hadoop Node Manager Monitors:

  1. Standard Monitor Name: Select the HadoopName Node Monitor.
  2. Instance Name: Instance name on which monitor should be configured.

58

HadoopNodeManger Monitor Parameters:

  • Hostname: Host name where hadoop server is running
  • Port Number: Port number to connect to hadoop’s (name node, data node, yarn, job tracker, task tracker)
  • Username: User Name for hadoop
  • Password: Password for hadoop
  • Retry count: Retry when connection lost
  • Enter sample interval in secs: Specify refresh rate to get data (in seconds)

3.  Then click “OK”.

Hadoop Resource Manager Queue:It monitors Applications Active,Applications Completed, Applications Failed, Applications Killed, Applications Pending etc.

Steps to add the hadoop Resource Manager Monitors:

  1. Standard Monitor Name: Select the HadoopResourceManager Monitor.
  2. Instance Name: Instance name on which monitor should be configured.

87

HadoopResourceManger Monitor Parameters:

  • Hostname: Host name where hadoop server is running
  • Port Number: Port number to connect to hadoop’s (name node, data node, yarn, job tracker, task tracker)
  • Username: User Name for hadoop
  • Password: Password for hadoop
  • Retry count: Retry when connection lost
  • Enter sample interval in secs: Specify refresh rate to get data (in seconds)

3.  Then click “OK”.

VMware ESXi(ESX) Monitor

VMware ESXiis an enterprise class, type-1 hypervisor developed by VMware for deploying and serving virtual computers.

Monitor list specific to VMwareExi:

VMwareExiCPU Stats Monitor: It gives ESXi VM CPU Statistics.

Steps to add: Follow the steps mentioned in “Adding VMwareExiCPUStats    Monitors” and bring data for CPU Usage (Percentage),CPU Usage in MHz, CPU Utilization, CPU Core utilization, Total CPU capacity in MHz.

Follow the steps mentioned below:

  1. Standard Monitor Name: Select the VMWxiCPUStats
  2. Instance Name: Instance name on which monitor should be configured.
  3. VM Name: Particular VM Name

59

VMWxiCPUStats Monitor Parameters:

  • Url: VMWare ESXi connector URL.
  • UserName: VMWare ESXi User Name
  • Password:Password of user name
  • VMName:VMWare Name
  • Retry Count: Retry when connection lost
  • Enter the sample interval in Sec:Specify refresh rate to get data (in sec)

4. Then click “OK”.

VMwareExiDisk Stats Monitor: It provides ESXi VM Disk information

Steps to add: Configuration for this monitor is same as the above VMwareExiCPUStats Monitor and brings the data for Disk Write Rate, Disk Read Rate and Highest Disk Latency.

VMwareNetwtork Stats Monitor: It gives ESXi VM network Statistics.

Steps to add: Configuration for this monitor is same as the above VMwareExiNetworkStats Monitor and brings the data for Data receive rate, Network Usage, Data transmit rate.

VMwareExiMemory Stats Monitor: It gives ESXi VM Memory

Steps to add: Configuration for this monitor is same as the above VMwareExiMemoryStats Monitor and brings the data for Memory Consumed, Active   write memory, Memory Granted, Memory Unreserved, Low free threshold, Memory Usage, Memory Active, Memory Heap Free(KB), Memory Used by vmKernel, Memory Shared Common (KB).

VMwareExiCPU Stats Monitor: It gives ESXi Host CPU stats

Steps to add: Configuration for this monitor is same as the above VMwareESXi Host CPU Stats Monitor and brings the data for CPU Usage (Percentage), CPU Usage in MHz.

GigaSpace Server

Monitor list specific to GigaSpace Server:

GigaSpaceDBStats: GigaSpace stats monitor communicates with server via REST API (http connection) to get stats of Database Connection metrics.

Steps to add: Follow the below mentioned steps:

Enter the following parameters, click the Add button, and then click the Save button.

  1. Tier Name: Select the Tier Name with Which the Server in mapped.
  2. Server Name: Select Server Name or IP address of machine where monitor is running.
  3. GDF Name: GDF name for which monitor should be configured.
  4. Vector Name: Provide the vector name to diffrenciate the monitor
  5. Option: NetStorm will start the monitor once at the start of Test Run. Run Once
  6. Program Name: Program for running the monitor.

/apps/java/jdk1.7.0_71/bin/java cm_gigaspace_db_stats -U http://10.10.30.25/gigaupdate -S connection -D -N

60

Weblogic JMS Queue Stats

It monitors different statistics of JMS Server Queues such as Number of Consumer Accessing Queue, Bytes Received in Queue, Message Received in Queue, Number of Messages Pending in Queue, Maximum Number of Message in Queue, Number of Messages Received in Queue, Bytes Stored in Queue, Maximum Bytes Stored in Queue, Pending Bytes in Queue, Bytes Received in Queue, BytesThresholdTime.

Steps to add: Follow the below mentioned steps:

Specify the following parameters detail.

  • Tier Name: Select the Tier Name with Which the Server in mapped.
  • Server Name: Select Server Name or IP address of machine where monitor is running.
  • Instance Name: Instance name on which monitor should be configured.
  •  Monitor Type: Select WeblogicJMSQueueStats Monitor, window will be displayed.

61

Weblogic JMS Queue stats Parameters

  • JmS Server: Enter the JMS Server name.
  • Module: Enter the module name.
  • Queue: Enter the Queue name.
  • Enter the sample interval in sec

Hbase Server

Hbase Monitor is used to monitor statistics of Apache Hbase Server stats like that for Hbase master, Region Server and Zookeeper.

Heroku Monitor

Heroku Monitor needs to monitor Heroku Server through Dyno Memory and Load Average. Dyno memory brings data for Dyno Total Memory (MB), Dyno Total Memory (MB), Dyno Resident Set Size (MB), Dyno Memory Cache(MB), Dyno Swap Memory(MB), Dyno Page Written to Disk, Dyno Page Read from Disk. Load Average brings data for Dyno Load Average (over 1m), Dyno Load Average (over 5m) and Dyno Load Average (over 15m).

AccessLogCustomStats Monitor

It monitors service time and request rate per status code series for user specified URL(s) or/and overall URL(s) from Access logs.

VHQ Log Monitor

Verifone Head Quarter Service generates the logs; those logs need to parse to calculate the following fields:

  • Requests/sec
  • Encryption Time (ms)
  • Decryption Time (ms)
  • POS Authentication Time (ms)
  • Response Time (ms)

Redis Monitor

Redis is a popular in-memory key/value data store. Known for its performance and simple onboarding, Redis has found uses across industries and use cases, including as a Database, Message queue, Memory cache.

Heap Object Stats Monitor

This monitor is introduced to capture stats of java heap objects for a running java processes. This monitor will fetch data and give number of current heap objects (instances) with their size, of required java class in a running JVM. Monitor will give stats corresponding to any java class or multiple java class or all class. Since PID of some java process keep changing after sometime therefore an option is provided to get PID based on specific pattern.

Heroku Access Log Monitor

In the current implementation, user can configure access log monitor for Heroku by specifying file name, that get created while dumping the logs. This will result in parsing the same line twice. As when we receive the data on socket, Heroku thread in LPS dump the data in file. Configuring access log monitor this way has overhead of opening file and parsing the data line.

This monitor will be configured either as Dynamic Vector Monitor or a Standard Monitor. Dynamic monitor configuration will be done as in case of access log monitor.

Standard Monitors – Following Standard Monitors will be provided.

  • HerokuAccessLogStats
  • HerokuAccessLogStatsExtended
  • HerokuAccessLogStatsExtendedV2

 MS SQL Store DB Windows Monitor

This monitor is introduced to measure health of MS SQL Database on windows server.

Network Delay Windows Monitor

The key objective behind Windows Network Delay Monitor is to ensure the availability and smooth operations on a computer network. Windows Network Delay Monitor deals with analyzing network traffic. It should capture packet lost, packet received stats.

Currently CavMonAgent is not able to get Networking stats of one windows server from another windows server. To capture Network metrics like Network Delay, Packet Lost etc., we will implement Windows Network Delay Monitor.

Apache Solr Monitor

The key objective of this Monitor is to get the Apache Solr statistics using Mbean server connection with JMX.

Apache Solr is an open source search server. It is based on the full text search engine called Apache Lucene. Solr is a popular search platform for Web sites because it can index and search multiple sites and return recommendations for related content based on the search query’s taxonomy. Solr is also a popular search platform for enterprise search because it can be used to index and search documents and email attachments. Solr works with Hypertext Transfer Protocol (HTTP) Extensible Markup Language (XML).

Docker Monitor

This is a shell based monitors introduced for Docker. Docker is an open source platform for developing and running applications. Docker runs any applications as a light weight container. Docker uses LXC container to support strong process isolation. Docker uses aufs file system for persisting the files.

Server Signature

Server Signature is to take the snapshot of the server configuration before test is started. It is very useful to compare server configuration in two different tests.

Types of Server Signature

Command Type: This type of server signature helps to execute the command on destination side and get the output of that command on the client side. For Example: To get the output of the command “ps –lef” from the destination side put this command in the Command field.

Add the command type server signature according to the server’s OS.

CommandServer’s OS
ps –lefLinux
/usr/ucb/bin/ps –axuwwwwwSun OS
df –hLinux and Sun OS both

Enhancement: Auto_server_signature setting is used to enable the auto server signature for the server i.e. this setting automatically enables the server signature according to the server’s OS type. 

File Type: This type of server signature helps to get the content of the specified File that is present on the destination side. For Example: To get the content of any file “abc.log” from the destination side put this file name in the Command field. The created file is present at the location: $logs/TRXXX/server_signatures/signature_name.ssf

Adding the Server Signature

Steps to Configure the Server Signature:

  1. Click on Server Signature, following window is displayed:

 

64

  • Tier Name: Select the Tier name on which you want to add the server signature.
  • Server Name: Select server which you want to monitor.
  • Signature Name: Enter the name of the signature.
  • Signature Type: Select Signature type either File or command.
  • Command name/File name: Enter Command name/File name of the program name and argument of dynamic monitor like –i (for interval).
  • Click on Add then Save button.

Note: If user has taken signature type as Command then he will have to give command and if has taken signature type file then he will have to give file.

Check Monitors

Check monitors are used for running user specified commands or programs on the server itself. Typical uses are to get server logs, check the status of the servers which Cavisson appliances are hitting to make sure servers are healthy during the test run.

This monitor is used to get data from server to Cavisson appliances.

Check monitor can be added in four places:

  • Before the start of the test
  • At start of the test
  • On start of a phase
  • At end of test

Generally, monitors are used at “Before the start of the test” and “at the end of the test” phases.

Adding the Check Monitors

Steps to configure the Check Monitors

  1. Click on Check Monitors, following window is displayed:

65

Figure 64: Check Monitors

  • Tier Name: Select the Tier name on which you want to add the Check Monitor.
  • Server Name: Select server which you want to monitor.
  • Monitor Name: Enter the name of the Monitor.
  • Description: Following From Event as follows:
    • Before start of test (1):- Frequency ‘Run Periodic’ does not support. It will get the data before start of the test.
    • At start of test (2):-It will get the information at Starting of Test. This supports the frequency value ‘Run periodic’ or ‘never’.
    • On start of a phase (3):- it will get data on Starting of phase. This will also support the frequency values.
    • At end of test (90):- Frequency ‘Run Periodic’ does not support. It will get data after test run is complete.
  • Check monitor program name: Program name and arguments of the Check Monitor.
Example for Program name: chm_get_server_logs -f /home/netstorm/work/file3.txt -n CheckMonitor

In this,

 chm_get_server_logs is the program name.

-f is used to import file we can also import the directory using –d.

/home/netstorm/work/file3.txt is the file argument path .

-n is used for defining the name of the TAR file.

ImportFile is the name of the TAR file that will be created into the $logs/TRxx/server_logs/servername/ImportFile.tar file.

2. Click on Add, then Save button.

Process Related Monitors

Process related monitors are those monitors that provide process related stats. There are following types of process monitors:

Process Data Monitor (ProcessDataEx)

ProcessDataEx monitor is extension of ProcessData monitor. It provides all information of ProcessData Monitor along with CPU Time (pct), Memory Used (pct) and Number of Threads.

Steps to add: Follow the steps mentioned in “Adding System Related Standard Monitors” and then follow the steps mentioned below:

  1. In this, add the Instance name also in which they want to setup the ProcessDataEx monitor.

66

ProcessDataEx Monitor Parameters:

  • Use process Id file: give the file name having the process id.
  • Use command to get the process Id: give the command to get the process id.
  • Process Id: Give the process id directly.
  • Search process using search pattern: give the Pattern for searching the process.
  • Select particular occurrence of process Occurrence count (ORD): give the count for the particular occurrence of the process.
  • Enter Sample interval in secs: interval in second.

2. Then Click the OK button.

Java GC Monitor

GC monitoring is done using GC log file or using JMX log file.

Commands to find the GC log file: Execute the command according to the JVM used by the Application.

JVMCommands
Sunps –ef | grep Xloggc
JRockitps –ef | grep Xverboselog
IBMps –ef | grep Xverbosegclog

Command Output: The JVM Argument (Xloggc, Xverboselog, Xverbosegclog) is followed by the path of the GC log file.

JavaGCJrockit: It provides the information about the Java garbage collector (GC) that how many GC occurred in specified interval, time used by GC and JVM memory usage.

JavaGCExtended: This is a Detailed Java Garbage Collector monitor. It monitors number of Java GC, time used in GC for Young and Tenured GC and JVM memory usage for Young, Survivor, Tenured and Permanent generation.

JavaGCJMX: It is used to get the GC stats via JMX port.

JavaGCJMXJrockit: It is used to get the Jrockit JVM stats via JMX Port.

Log Related Monitors

Log data stream monitor is used to abstract useful information from log file. It shows data in graphs as per GDF. It parses the information from log file (updating) while test is running.

LogPatternMonitor: It reads the user defined file (updated regularly) and returns rate of “Number of occurrence” and “Total Number of occurrence” of search pattern.

LogDataMonitor: Log File Data monitor is used to get average of any numeric field. It can be used in three ways.

  • Field Number
  • Pattern
  • Field Number & Pattern

LogEventMonitor: It is used to get the count of a specific pattern.

GetLogFile: It is used to get log file updated for test run duration from server.

Server Related Monitors

App Servers

There are the following types of App Servers:

Type of App ServerMonitors
Weblogic Server 

WeblogicJDBCStats

WeblogicJVMStats

WeblogicSessionStats

WeblogicThreadPool

AccessLogExtended

 

JBoss Server 

JBossServletStats

JBossThreadPoolStats

 

Websphere Server 

WebsphereJDBCStats

WebsphereSessionStats

WebsphereServletStats

WebsphereThreadPoolStats

 

SpringDM Server 

SpringDmExecutorServicesStats

SpringDmJKHandlerStats

SpringDmRequestProcessorStats

SpringDmServletStats

SpringDmThreadingStats

SpringDmThreadPoolStats

SpringDmWebModuleStats

SpringTCExecutorStats

SpringTCServletStats

SpringTCThreadPoolStats

 

Coherence Server 

CoherenceCacheExCumStats

CoherenceClusterNodeStat

CoherenceCacheExStats

 

Weblogic Server

For setting up monitors on these servers, user need legitimate credentials to access Weblogic admin console (can be read only) which can be obtained by placing service request to client.

WeblogicJDBCStats: It provides information about different statistics of JDBC connection pool such as active connection, delay time and failures.

WeblogicJVMStats: It provides the information about different statistics of JVM i.e. Heap Free Memory, Current Size and uptime.

WeblogicSessionStats: It provides information about different statistics of Sessions i.e. Session count, Session high count, Total Session Count.

WeblogicThreadPool: It provides information about different statistics of thread pool such as execute thread count, hogging thread and it also configure same as above WeblogicJdbcStats.

AccessLogExtended: It is used to parse access log file and return number of requests, throughput and average service time segregated by different HTTP status code.

JBoss Server

JBossServletStats: It monitors number of minTime, processingTime, maxTime, errorCount, loadTime, classLoadTime, requestCount counters.

JBossThreadPoolStats: It monitors number of maxThreads, backlog, currentThreadsBusy, acceptorThreadCount, threadPriority, currentThreadCount counters.

Websphere Server

For setting up monitors on these servers, user needs legitimate credentials to access Weblogic admin console (can be read only) which can be obtained by placing service request to client.

WebsphereJDBCStats: It provides statistics of websphere jdbc details.

 

WebsphereSessionStats: It provides statistics of websphere session stats details.

WebsphereServletStats: It provides statistics of websphere servlet details.

WebsphereThreadPoolStats: It provides statistics of websphere thread pool details.

SpringDM Server

SpringDmExecutorServicesStats: It provides statistics of spring dm server executor services details.

SpringDmJKHandlerStats: It provides statistics of spring dm server JKhandler details.

SpringDmRequestProcessorStats: It provides statistics of spring dm server request processor details.

SpringDmServletStats: It provides statistics of spring dm server servlet details.

 

SpringDmThreadingStats: It provides statistics of spring dm server threading details.

SpringDmThreadPoolStats: It provides statistics of spring dm server threadpool details.

 

SpringDmWebModuleStats: It provides statistics of spring dm server web module details.

 

SpringTCExecutorStats: It monitors number of poolSize, largestPoolSize, activeCount counters.

 

SpringTCServletStats: It monitors number of minTime, processingTime, maxTime, errorCount, loadTime, classLoadTime, requestCount counters.

SpringTCThreadPoolStats: It monitors number of maxThreads, backlog, currentThreadsBusy, acceptorThreadCount, threadPriority, port, soLinger, soTimeout currentThreadCount counters.

Coherence Server

The Coherence Monitors can be implemented on Weblogic and Websphere servers.

CoherenceCacheExCumStats: It provides statistics of coherence cache cumulative details.

CoherenceClusterNodeStat: It provides statistics of coherence cluster node details.

CoherenceCacheExStats: It provides statistics of coherence cache details.

Web Servers

There are the following types of Web Servers:

Type of Web ServerMonitors
Apache Server 

AccessLogExtended

ApacheServerStatus

JKApacheServerStat

 

ApacheSolr 

ApacheSolrCache

ApacheSolrCacheEx

ApacheSolrQueryHandler

ApacheSolrUpdateHandler

 

Apache Server

AccessLogExtended: For access log extended, first, user need to check the log format on the servers.

Log format of Webservers (Apache): “%h %l %u %t \”%r\” %>s %D %b \”%{Referer}i\” \”%{User-Agent}i\”” combined

Description of Log Format Fields:

Field NameField SequenceDescription
Opening quotes
%h1This is the IP address of the client (remote host) which made the request to the server.
%l2Remote Logname
%u3This is the userid of the person requesting the document.
%t4The time that the request was received.
\”%r\”5The request line from the client
%>s6This is the status code that the server sends back to client.
%D7The time taken to serve the request, in microseconds.
%b8The size of the object returned to the client
\”%{Referer}i\”9It is used for Reference.
\”%{User-Agent}i\”10It is used for User- Agent.
Closing quotes

If this is not matched with the server config file, need to make a request to the support/client team. Details are described above in Weblogic Server.

ApacheServerStatus: This is used to monitor status of apache server.

 

JKApacheServerStat: This is used to monitor jk status of apache server.

ApacheSolr

ApacheSolrCache: It provides statistics of apache solr stats details.

ApacheSolrCacheEx: It provides statistics of apache solr stats details.

ApacheSolrQueryHandler: It provides statistics of apache solr query handler stats.

 

ApacheSolrUpdateHandler: It provides statistics of apache solr update handler stats.

Database Servers

There are the following types of Database Servers:

Type of Web ServerMonitors
Oracle Database Server 

OracleStats

 

Cassandra Server 

CassandraColumnFamilyStats

CassandraCompactionStats

CassandraNodeStats

CassandraThreadPoolMsgStats

CassandraThreadPoolStats

 

Endeca Server 

EndecaStatsDVM

 

Oracle Database Server

Generation of AWR Report

The awr*.html FilePath on Database server is needed and the file updation is mandatory. If the file is not updated within some interval of time, need to make request to start some cron job to update that file to the support team. Or it is needed to make some shell by using nsu_server_admin to update that file.

OracleStats: This is used to monitor Oracle database server status.

Cassandra Server

CassandraColumnFamilyStats: It provides statics of tables or schemas created in cassandra database.

CassandraCompactionStats: It provides statics of number of tables merged or compaction.

CassandraNodeStats: It provides statics of uptime in seconds,load and heap memory usage by cassandra database.

CassandraCompactionStats: It provides statics of number of tables merged or compaction.

CassandraNodeStats: It provides statics of uptime in seconds, load and heap memory usage by cassandra database.

CassandraThreadPoolMsgStats: It provides statics related to number of read, write, binary etc messages dropped.

CassandraThreadPoolStats: It displays the number of active, pending, and completed tasks for each of the thread pools.

Endeca Server

EndecaStatsDVM: It monitors service time, processing time, request queued, idle threads, throughput, successful request rate per minute and failure request rate per minute for user specified URL(s) or/and overall URL(s) from endeca request logs.

Windows Servers

  • ProcessorStats
  • WinSystemStats
  • MemoryStats
  • LogicalDiskStats
  • ProcessStats
  • .NETCLRMemoryStats
  • .NETDataProviderForSqlServerStats
  • .NETCLRSecurityStats
  • .NETCLRRemotingStats
  • .NETCLRLocksAndThreadsStats
  • .NETCLRLoadingStats
  • .NETCLRJitStats
  • .NETCLRInterropStats
  • .NETCLRExeptionsStats
  • W3SVCWebServiceStats
  • TCPIPTCP4Stats
  • ASPActiveServerPagesStats
  • SQLServerAccessMethods
  • SQLServerBufferManager
  • SQLServerPlanCache
  • SQLServerDatabase
  • SQLServerGeneralStatistics
  • SQLServerLocks
  • SQLServerMemoryManager
  • SQLServerSQLStatistics
  • SQLServerSQLWaitStatistics
  • SQLServerLatches
  • ASPNETStats
  • #ASPNETStats64
  • ASPNETStats64V4030319
  • ASPNET64BITStats
  • ASPNETStats64V2050727
  • AppPoolWASStats
  • HTTPServiceUrlGroupsStats
  • IPHTTPSGlobalStats
  • TCPIPNetworkInterfaceStats
  • PhysicalDiskStats
  • W3SVC_W3WPStats
  • WebServicesStats
  • CacheStats
  • PagingStats
  • ProcessorInfo
  • ServerStats