The following guides you to additional agent configuration options that can help you tailor the level of monitoring for Java applications. It includes collection of SQL parameters, collection of HTTP parameters and header data, extraction of user IPs, selection of user count tracing method, SAP function tracking, and the like. Through these options, more granular data collection and analysis can be tailored, especially in security-critical environments.
The following explains how to configure the network to transmit the data collected by Java agents from the application servers to the server. The major configuration options are the collection server host, port, timeout value, network transfer size, and data transfer queue size, which are important to ensure the agent's efficient data management and reliable server communication.
It describes the connection settings between the agent and the server.
The following explains how to configure the Java agent. The whatap.conf file includes the agent's default settings, server connection and data transfer settings, and how to manage the configuration files for multiple application servers. It also provides the way to manage the agent options directly on the WhaTap monitoring service screen.
It provides the method how to delete the Kubernetes agent.
This FAQ document is related with the WhaTap agent.
The following guides you to the basic installation method for using the WhaTap database monitoring service.
The following guides you to the basic installation method for using the WhaTap database monitoring service.
All the steps to install WhaTap's Java application monitoring agent are explained in detail. This section explains how to download and install the agent and how to set the configuration files including the agent's default settings.
It describes the steps to install an agent for Kubernetes monitoring.
The following guides you to the basic installation method for using the WhaTap database monitoring service.
The following guides you to the basic installation method for using the WhaTap database monitoring service.
The following guides you to the basic installation method for using the WhaTap database monitoring service.
Let's learn how to create a project and install the agent in the WhaTap monitoring service.
The following guides you to the basic installation method for using the WhaTap database monitoring service.
Check the agent installation method that can be applied to the application server that runs in the PHP environment.
The following guides you to the basic installation method for using the WhaTap database monitoring service.
The following guides you to the basic installation method for using the WhaTap database monitoring service.
The following guides you to the basic installation method for using the WhaTap database monitoring service.
The following explains how to manage log data generated in the Java application environment through the agent. It includes the configuration of the path and name of the log file, retention period setting, log monitoring, and how to enable custom log tracing. It also provides various options for log management to help manage system logs efficiently.
The following explains how to set the agent name in order to identify the monitoring target.
To identify monitoring targets, the method how to set a unique identifier for the application server is provided. It is required to identify application servers among the monitoring target systems. You can see automatic naming based on the data such as server type and IP. Otherwise, you can manually set the agent name through the whatap.conf file or JVM options.
The following explains how to set the agent name in order to identify the monitoring target.
The following explains how to set the agent name in order to identify the monitoring target.
The following explains how to set the agent name in order to identify the monitoring target.
The following lists the settings related to network communication of the database agent.
The following lists the settings related to network communication of the database agent.
The following lists the settings related to network communication of the database agent.
The following explains how to configure notifications for various events that occur in the application server through Java agents. It includes the options to configure event notifications for transaction recursive calls, denial of service, HTTPC connection errors, excess of heap and disk usage, CPU usage threshold violation, DB connection duplicate allocations, and exceptions. For each event, you can make detailed adjustments such as release interval, release status, and threshold settings.
The following guides you to the performance options for Java agents. You can check the maximum number of transactions that can be processed simultaneously and the initial size of the buffer that stores transaction data. This plays an important role in optimizing the system load and resource usage.
The following explains the procedure how to uninstall a Java agent or revert to a previous version. The procedure to delete an agent includes removing the -javaagent JVM option and restarting the server and cleaning up the environment variables.
The following explains how to update the Java agent to the latest version. The procedure includes how to download the latest agent and restart the application server to apply the update. For a stable system shutdown, you can see the procedure for terminating Apps, changing the agent JAR file, and updating status during the startup.
Page Load events are provided in a chart, and the detailed information about events can be analyzed.
The following describes the Java agent options that set Apdex scores to measure the user satisfaction. Apdex metrics help you objectively evaluate the application's performance and improve user experience.
Apply the WhaTap browser agent to your web application and start the browser monitoring.
The following explains how to trace activities of asynchronous applications through the Java agent settings. It includes the methods for collecting CompletableFuture methods and hooking those methods into user applications. It provides the options to add to the whatap.conf file along with configuration examples, to help enhance performance monitoring for asynchronous calls.
The following explains how to automatically delete the Java agent when an automatically scaled system performs Scale In in the Auto Scale environment. The agent sends a SILENT_SHUTDOWN event to the server by creating a specific file, which automatically removes the agent from the list. This process facilitates agent management when the system automatically scales down, and manages resources efficiently without additional intervention.
The following explains how to apply WhaTap's Java agent to batch applications. It also describes how the batch applications differ from web applications due to unique repetitive start and stop operations, and provides the methods for downloading the required agents, configuring agents and batch hosts, running batch jobs with agents, and monitoring the execution times by setting the time_limits.
It is a description of the data collected by the WhaTap browser agent.
To identify the web service issues and improve user experience through browser monitoring, it provides an interface that allows developers and operators to additionally collect desired events that occur on web pages.
The description of the settings to collect data from the database server
The description of the settings to collect data from the database server
The description of the settings to collect data from the database server
The following explains how the Java agent collects CPU, memory, and disk usage. Java's JMX library is basically used. If necessary, you can see how to collect performance metrics through Linux's proc directory or oshi and sigar libraries.
description
You can collect various metrics from OpenTelemetry through the agent settings.
The following explains how to fine-tune the agent functionality for monitoring Java application servers. It includes the functions such as enabling/disabling agents, tracing transactions and performance counters, and collecting OS data. You can see various setting options that control each function.
The following provides various options for Java agents to handle the database and collect SQL performance data. They can trace various DB connection pools such as DBCP, Hikari, and Tomcat and record SQL execution details. Additionally, it provides information collection options for performance optimization, such as recording SQL parameters and tracing DB connection leaks.
The following provides the options you can set through the whatap.conf file on the MongoDB database.
The step-by-step instructions on how to apply the WhaTap Java monitoring agent to Java applications in the Docker environment are provided. Users can add more Whatap Java agent settings to the existing Docker image to see the processes for building a new image, creating the whatap.conf file, writing a Dockerfile, and modifying JAVA_OPT. Additional JVM options for Java 17 or later and the method how to configure the heap histogram lookup for various Java versions are also provided.
The following explains users who run Java applications on the AWS Elastic Beanstalk environment on how to set JVM options to effectively apply WhaTap's Java monitoring agent. You can check the processes of installing and configuring WhaTap's Java agent in the Elastic Beanstalk and adding and configuring the required JVM options. Additionally, it includes the histogram query method.
The following explains how to set options for the Java agent to collect and analyze data for HTTP outbound calls and API calls. Various options for fine monitoring are provided such as TOO SLOW error handling, CPU and memory usage tracing, stack trace recording upon each call, and URL normalization. This allows developers to efficiently manage their applications' external dependencies and identify performance issues.
The following explains users who run Java applications on the IBM Bluemix cloud platform on how to set JVM options to effectively apply WhaTap's Java monitoring agent. Through this document, users can check step by step the processes of installing WhaTap's Java agent in the IBM Bluemix environment, configuring the agent, and adding the required JVM options. Additionally, it includes the histogram query method.
The database monitoring has been installed completely. Check the checklist after installation.
The database monitoring has been installed completely. Check the checklist after installation.
Important checks are described after installing the Java agent. They include verification for correctness of JAVA_OPTS settings, necessity for restart of the application server, and agent connectivity through the monitoring service.
The database monitoring has been installed completely. Check the checklist after installation.
The database monitoring has been installed completely. Check the checklist after installation.
The database monitoring has been installed completely. Check the checklist after installation.
The database monitoring has been installed completely. Check the checklist after installation.
The database monitoring has been installed completely. Check the checklist after installation.
The database monitoring has been installed completely. Check the checklist after installation.
The server monitoring has been installed completely. Check the checklist after installation.
The database monitoring has been installed completely. Check the checklist after installation.
Follow the installation guide to install the master and node agents.
The following explains how to configure the Custom Server for monitoring the Node.js applications in the server-side rendering (SSR) framework such as Next.js.
The following explains how to configure the Custom Server for monitoring the Node.js applications in the server-side rendering (SSR) framework such as Nuxt.js.
It guides you how to create a DockerFile in the Docker environment to install and run the Node.js agent.
It guides you how to install the Java agent using the buildpack.
The following provides the detailed guide on how to add Java Virtual Machine (JVM) options to integrate the WhaTap monitoring solution into JBoss applications. Through this document, users can learn step by step how to apply the required JVM settings to monitor the performance and availability of JBoss applications after installing the Java agent. It includes the configuration of essential JVM options during agent installation, optimal configuration for smooth integration with JBoss, and histogram query.
We provide detailed instructions on how to add the Java Virtual Machine (JVM) option to integrate the WhaTap monitoring solution into the Jetty applications. Through this document, you can learn step by step how to apply the required JVM settings to monitor the performance and availability for Jetty applications after installing the Java agent. It includes the configuration of required JVM options during agent installation, optimal configuration for smooth integration with Jetty, and histogram query methods.
The following provides the detailed guide on how to add Java Virtual Machine (JVM) options to integrate the WhaTap monitoring solution into JEUS applications. Through this document, users can learn step by step how to apply the required JVM settings to monitor the performance and availability of JEUS applications after installing the Java agent. It includes the configuration of essential JVM options during agent installation, optimal configuration for smooth integration with JEUS, and histogram query.
Let's learn about the configuration of the installed agent to monitor applications running in Kubernetes.
We provide detailed instructions on how to add the Java Virtual Machine (JVM) option to integrate the WhaTap monitoring solution into the Liberty applications. Through this document, you can learn step by step how to apply the required JVM settings to monitor the performance and availability for Liberty applications after installing the Java agent. It includes the configuration of required JVM options during agent installation, optimal configuration for smooth integration with Liberty, and histogram query methods.
This guide describes the agent options that configure the traffic throttling options for Java application servers. The following includes the features to limit the maximum number of concurrent requests for applications and control service accesses based on specific users or URLs. It provides various options such as sending custom messages, setting URL redirections, and enabling event notifications, to ensure stability of applications under overload situations.
Learn how to update or delete agents for the MongoDB database.
Learn how to update or delete agents for the Redis database.
You can use the okind JVM option to easily identify automatically registered Java agents for each business unit in the Auto Scale Out environment. This setting that is useful for agent management in the Docker environment, is useful to distinguish the agent's role or the service group.
It provides the configuration method how to trace frameworks or open source libraries used in Java applications through the agent. It is configured by adding the weaving option in the Java agent configuration file (whatap.conf). The guide on how to respond to various framework and library versions is also provided.
You can collect resource data from the AWS environment and display it on the topology screen.
The following explains how to add the Java Virtual Machine (JVM) option to integrate the WhaTap monitoring solution into the Play2 applications. Through this document, you can learn step by step how to apply the required JVM settings to monitor the performance and availability of Play2 applications after installing the Java agent. It includes the configuration of required JVM options during agent installation, optimal configuration for smooth integration with Play2, and how to view the histogram.
You can easily configure the agent by running the setup.sh file among the DBX agent configuration files.
We provide detailed instructions on how to add the Java Virtual Machine (JVM) option to integrate the WhaTap monitoring solution into the Resin applications. Through this document, you can learn step by step how to apply the required JVM settings to monitor the performance and availability for Resin applications after installing the Java agent. It includes the configuration of required JVM options during agent installation, optimal configuration for smooth integration with Resin, and histogram query methods.
The plugin option provided by the Java agent provides a way for you to inject desired code into the trace data or add additional information before and after execution of the method. It includes the options for setting where to run specific code at method entry/exit time and how to configure a class to monitor custom pools. More specific usages are provided through actual plug-in application cases, and it guides you to various configuration examples and API usage that can increase the flexibility and precision for monitoring.
In the browser monitoring, you can collect data by setting the user ID via the actual user's login ID or email address.
It explains how to apply the options to an agent for using the topology functions.
It explains how to apply the options to an agent for using the topology functions.
It explains how to apply the options to an agent for using the topology functions.
It explains how to apply the options to an agent for using the topology functions.
The following provides the detailed guide on how to add Java Virtual Machine (JVM) options to integrate the WhaTap monitoring solution into Spring Boot applications. Through this document, users can learn step by step how to apply the required JVM settings to monitor the performance and availability of Spring Boot applications after installing the Java agent. It includes the configuration of essential JVM options during agent installation, optimal configuration for smooth integration with Spring Boot, and histogram query.
The following guides you to the agent options for various statistics collections to monitor Java applications. It includes performance counter extensions, transaction collection by domain, multi-server transaction dependency analysis, statistics collection by login type and referral, and more. You can also check the maximum record limit settings for collecting SQLs, HTTP calls, error statistics, and user agent information.
The following provides the detailed guide on how to add Java Virtual Machine (JVM) options to integrate the WhaTap monitoring solution into Tomcat applications. Through this document, users can learn step by step how to apply the required JVM settings to monitor the performance and availability of Tomcat applications after installing the Java agent. It includes the configuration of essential JVM options during agent installation, optimal configuration for smooth integration with Tomcat, and histogram query.
The following guides you to the agent configuration options that use the data collected by the Java agent to create a topology map for applications. You can visualize and analyze the topology of your system through various metrics, such as transaction callers, database connection information, HTTPC outbound information, and active transaction status.
The following guides you to the agent configuration options that detect errors during transactions in Java applications and display stack traces. It collects errors from various areas such as transactions, methods, SQLs, HTTP calls, and SOCKET calls, and includes methods how to set the error stack length, title length, and such. It helps you improve error handling through agent settings and support more efficient error diagnosis for applications.
The following explains how to set an agent to trace and analyze performance data for each transaction within Java applications. It evaluates the application performance by tracing transaction requests, response time, and resource usage.
You can check the problems that may occur during database agent installation.
You can check the problems that may occur during database agent installation.
You can check the problems that may occur during MongoDB database agent installation.
You can check the problems that may occur during database agent installation.
You can check the problems that may occur during database agent installation.
You can check the problems that may occur during database agent installation.
You can check the problems that may occur during database agent installation.
You can check the problems that may occur during Redis database agent installation.
You can check the problems that may occur during database agent installation.
The following explains how to count the number of users connected to the Java web application server through agent settings. It includes the setting whether to enable real-time user counting, setting of the cookie limit to count users, the method how to count users based on the IP address or specific HTTP header values, and setting of HTTP headers to trace client IPs.
The description of the agent configuration using the AWS CloudWatch
The description of the agent configuration using the AWS CloudWatch
The description of the agent configuration using the AWS CloudWatch
The following explains how to apply the Java agent in versions lower than Java 1.6. You can see the agent installation and setup procedures for Java 1.5 and 1.4 respectively, as well as restrictions related to the -javaagent option.
The following provides the detailed guide on how to add Java Virtual Machine (JVM) options to integrate the WhaTap monitoring solution into WebLogic application. Through this document, users can learn step by step how to apply the required JVM settings to monitor the performance and availability of WebLogic applications after installing the Java agent. It includes the configuration of essential JVM options during agent installation, optimal configuration for smooth integration with WebLogic, and histogram query.
The following provides the detailed guide on how to add Java Virtual Machine (JVM) options to integrate the WhaTap monitoring solution into WebSphere applications. Through this document, users can learn step by step how to apply the required JVM settings to monitor the performance and availability of WebSphere applications after installing the Java agent. It includes the configuration of essential JVM options during agent installation, optimal configuration for smooth integration with WebSphere, and histogram query.
The following explains how to configure the database process monitoring.