When conducting load tests, you generate a load that the server must manage in a particular way. Using ReadyAPI, you may monitor a number of web server metrics to see if they are operating as you had anticipated. You utilize the Monitoring page to accomplish this. During a test run, ReadyAPI collects all available metrics from tested web servers. During the test run, ReadyAPI shows the most crucial information as graphs at the bottom of the page in real-time. You can see all of the gathered information on the Statistics page. Typically, it includes all of the test's statistics and server metrics, including the number of simulated users and server response time. Let us see different kinds of monitors available and used.
Windows Monitor
To inspect the metrics of your Windows-based servers, you utilize Windows monitors. This needs the following:
A Windows computer is required to execute ReadyAPI. On Linux and macOS computers, there are no Windows, IIS, or MSSQL monitors available.
The server's Remote Registry service needs to be activated.
The server, the machine running ReadyAPI Performance, and any proxy in between them must all have ports 139 and 445 accessible.
The server's Performance Monitor or Administrator rights must be granted to the user account.
Frequently Used Metrics
Other often used measures include the following:
Paging File – % Usage – Total – When your server's RAM is insufficient to handle all requests, the paging file is generated. The better, the smaller the file. Consider adding extra RAM if the paging file is around for a while.
Logical Disk – Free Megabytes – YourDiskName – Calculates the amount of free space on the hard drive. The server's storage needs are greatly influenced by its function. For instance, you won't require much free space if your server only processes requests for the website. However, if users have the option to upload files, you'll need a lot of capacity in case user numbers suddenly increase.
Unix Monitor
To inspect the metrics of your Unix-based servers, you utilize Unix monitors. This requires that Net-SNMP be installed and set up on the server as a requirement. The monitor can be configured as: The port used to communicate with the server is called a port. is set to 161. The preferred SNMP version is SNMP. Versions 1, 2c and 3 are supported by ReadyAPI.
The other parameters are based on the version of the SNMP protocol you use to connect to the server.
Frequently Used Metrics
Other often used measures include the following:
Disk – Total Size and Disk – Used – Count the amount of disc space that is consumed during the test run. You might need to add more storage if your tests are utilizing more than 80–90% of the disc space.
RAM – Total Size and RAM – Used – Calculate the RAM usage during a test run. Unix machines shift the least-used memory blocks to the virtual memory on the hard drive if your server doesn't have enough RAM. Because hard disc access is slower than RAM access, this could result in performance bottlenecks.
Apache Monitor
To inspect the stats of your Apache servers, you utilize Apache monitors. You must enable the mod status module in order to monitor the Apache server. The monitor can be configured as follows:
Port - The port used for server communication. Usually set at 80.
Connect through HTTPS - Indicates whether ReadyAPI will establish a secure connection with the server.
Use client SSL Auth - Indicates whether or not the SSL handshake's client authorization will be applied.
The location of the Apache Keystore, or the Keystore.
Keystore password - The Apache Keystore password.
Client auth password: The password used to obtain client authorization.
Frequently Used Metrics
Other often used measures include the following:
Basic - Idle Workers- The amount of available idle workers on the server is listed under Basic - Idle Workers. The client does not have to wait for the server to finish its current task before replying to the request as long as there are idle workers. Increase the number of permitted workers in the settings if there are no more idle workers. Hardware resources like memory and CPU are required by each worker, therefore you should also keep an eye on them.
Extended - Uptime: The amount of time the server has been operational. The majority of servers require routine rebooting in order to install updates and perform maintenance.
To collect metrics from your AppDynamics application using AppDynamics monitors. the following conditions must be met for this: Add one of the following roles to your API token: Authorized User, Administrator, Analytics supervisor, Viewer for Applications & Dashboards, Admin for Server Monitoring, and Obtrusive agent manager
The monitor settings include:
Host - The AppDynamics controller's address.
The authentication token is the token.
Application name - The title of the program to be watched.
Metrics - A list of the AppDynamics metrics you'll use.
Update rate: How frequently should ReadyAPI access the AppDynamics server for data? (in seconds).
Available metrics
All of the metrics offered by the AppDynamics APM platform are obtained by ReadyAPI.
The most well-liked measures are shown below, with default values:
Calls per Minute - The overall number of business transactions that are executed each minute.
Overall Application Performance|Average Response Time (ms) - The typical amount of time needed to complete a transaction each minute.
Overall Application Performance|Average End-to-End Latency (ms) - The typical amount of time required to process end-to-end message transactions
IIS Monitor
To inspect the metrics of your IIS servers, you utilize IIS monitors. An IIS server must be prepared for monitoring in the same way that Windows servers are for testing:
Windows computers are required to run ReadyAPI. On Linux and macOS computers, there are no Windows, IIS, or MSSQL monitors available.
On the server, the Remote Registry service needs to be turned on.
On the server, the PC running ReadyAPI, and any proxy in between, ports 139 and 445 must all be open.
The server's Performance Monitor or Administrator rights must be granted to the user account.
Frequently Used Metrics
Other often used measures include the following:
Web Service - Service Uptime - Calculates how long the server has been operational. The majority of servers require routine rebooting in order to install updates and perform maintenance.
The number of requests that failed because the requested resources were already in use is measured by the Web Service - Locked Errors/sec metric.
Current File Cache for Web Services Measures how much RAM is being used by the web service cache. To improve access speed, the files are cached.
MongoDB Monitor
To inspect the metrics of your MongoDB databases, you utilize MongoDB monitors. For this, the monitor's settings are port, username, password, and database.
Frequently Used Metrics
Database metrics for MongoDB provide details on how the database was used during the test run. By default, ReadyAPI shows the following statistics in charts:
The total number of queries that were made to the database throughout the test run. The majority of the time, database queries require reading data from the hard disc. The speed of the searches that use cached data is substantially higher.
Virtual memory consumed by the MongoDB process is indicated by memory utilization.
MSSQL Monitor
To inspect the metrics of your MSSQL databases, you use MSSQL monitors. The conditions are as follows:
A Windows computer is required to execute ReadyAPI. On Linux and macOS computers, there are no Windows, IIS, or MSSQL monitors available.
The server's Remote Registry service needs to be activated.
The server, the machine running ReadyAPI Performance, and any proxy in between them must all have ports 139 and 445 accessible.
The server's Performance Monitor or Administrator rights must be granted to the user account.
Frequently Used Metrics
Other often used measures include the following:
SQLServer: SQL Errors - Errors/sec - Total - The total amount of SQL errors occurring each second. The better, the lower this value should be.
SQLServer: Wait Statistics - WaitType - Average wait time (ms) - The typical amount of time needed to process database requests
SQLServer: Delay Statistics - WaitType - Waits in Progress - The total number of active waits for each type of wait. If you simulate a sudden rise in load, this value might increase, although it should typically be quite modest.
SQLServer: Memory Manager - Free Memory (KB) - Indicates how much memory is available but not being used by the database.
Memory Manager for SQLServer: Granted Workspace The amount of memory that is currently being used to work with the database is measured in KB. To determine how much memory the database uses, add this value to the Free Memory (KB) statistic.
MySQL Monitor
To inspect the metrics of your MySQL databases, you utilize MySQL monitors. Port, username, and password options are available for the monitor.
Frequently Used Metrics
Other often used measures include the following:
Query cache – Qcache_hits –The number of searches that match cached files is measured by Qcache hits. Although comparing cached files is quicker, your server can only hold so many cached files, therefore the ratio is crucial.
IO - Bytes sent and IO - Bytes received- These statistics indicate how many bytes your server sent and received. Your server might not have the capacity to manage the required throughput if there are too many requests. You will require a stronger Internet connection in this scenario.
WildFly (JBoss) Monitor
To check the metrics of your WildFly servers, you utilize WildFly monitors. the conditions for this are To install the ReadyAPI, and place the jboss-cli-client.jar library in the bin/ext installation folder. For a connection to the server, utilize the management user account. Port, username, and password options are available for the monitor.
Frequently Used Metrics
The quantity of threads created on a virtual machine is known as VM Threading - Thread Count. Keep an eye on this metric to learn how many new threads were created.
The amount of virtual machine memory that the server has utilized to process requests is known as the VM Memory-Used.
Tomcat Monitor
To inspect the metrics of your Tomcat servers, you utilize Tomcat monitors. Port, username, and password options are included for the monitor.
Frequently Used Metrics
Other often used measures include the following:
Current Threads in the Thread Pool The proportion of active threads on the server that is busy. To determine the relative usage of the threads, keep an eye on these indicators.
The garbage collector process is given top priority in the system. VM Garbage Collector - Collection Time Your machine has fewer resources to handle incoming requests if it spends a lot of time gathering garbage.
Frequently Asked Questions
How does the ReadyAPI platform from SmartBear differ from other platforms for testing APIs like SoapUI Pro?
With all the features of SoapUI Pro plus added capacities for load testing, security testing, and virtualization, ReadyAPI is a comprehensive platform for API testing. Additionally, ReadyAPI includes a more user-friendly interface that makes it simpler to begin API testing.
What are some of ReadyAPI's key characteristics?
It has tools for building test plans, executing tests, and producing reports. Additionally, it has a mocking tool that can be used to replicate API replies when testing.
Can Groovy scripts be used in ReadyAPI tests? In that case, how?
Yes, Groovy scripts can be used in ReadyAPI testing. This can be done by including a Groovy script test step in your test case.
Conclusion
To conclude this blog, we discussed monitoring servers. Then we saw different monitor servers and discussed monitor servers, their requirements, monitor settings, and frequently used monitor. Different monitoring servers include windows monitors, Unix monitors, Apache monitors, AppDynamics monitors, IIS monitors, MongoDB monitors, MSSQL monitors, MYSQL monitors, WildFly monitors, and Tomcat monitors.
46+ registered 