Skip to main content
Intelligent Monitoring | Performance management
Need to monitor system performance to ensure stable system operation?
JP1/Performance Management monitors and collects information about all of the different parts of your system, helping you to keep it running smoothly.
JP1 can be used in both on-premises and cloud environments to efficiently monitor different kinds of nodes without the use of specialized monitoring tools. With JP1's diverse functions, you can evaluate your system's relative performance, by comparing, along a timeline, your system's operating status against accumulated operational data from the past. This makes it easier to identify areas that are likely to become future bottlenecks and allows you to perform capacity planning without relying on instinct alone.
With JP1, you can monitor information pertaining to operating systems, databases, applications of all kinds, virtual environments, and more?all from a single window. For server-based applications, you can perform alive monitoring of processes and Windows services, and even monitor the operation of individual processes. Setting multiple thresholds at different levels allows you to check, in real time, thresholds that are about to be exceeded or have already been exceeded. This in turn helps you to predict degradation in system performance before it happens and, when a problem occurs, to determine the process or application causing the degradation. Because JP1 can be used to monitor operating information collected by most other management products or by management tools unique to your system, you can monitor your system in a way that suits your needs. In addition, accumulating data about day-to-day operations allows you to assess system performance by comparing current data with past data, and to identify areas that are likely to cause bottlenecks in the future. These and many other functions help you take the necessary measures (for example, upgrading servers or adding disks) at the right times to prevent problems such as those resulting from insufficient resources or poor performance.
You can configure JP1 to monitor your system in a way that suits your monitoring requirements and the nodes to be monitored. For example, JP1 allows you to use a combination of agentless and agent-based monitoring in the same environment, giving you the flexibility to choose how to monitor each server based on its level of importance.
Agentless monitoring allows you to monitor servers without installing agents on those servers. This can be an effective solution when you want to introduce JP1 products into an existing system and start monitoring immediately. Agentless monitoring also places less of a load on monitored servers as compared to agent-based monitoring.
<Features of agentless monitoring>
Agent-based monitoring involves installing agent software on the servers that you want to monitor. This type of monitoring provides more detailed information about the operating statuses of servers, and works even when the monitored server is disconnected from the network or when the performance monitoring software is not running. Thus, agent-based monitoring is especially useful when you want to comprehensively monitor a particular group of servers.
<Features of agent-based monitoring>
JP1 offers many useful templates, such as those that define the appearance of reports on monitored information and those for configuring alarms that notify administrators when critical thresholds or warning-level thresholds have been exceeded. These templates help you start monitoring your assets right away and can be easily customized for even better integration with your system.
Use the icons in the Quick Guide window to easily perform actions such as configuring monitoring settings and displaying reports. To easily find and select the information you want to monitor, you can specify a keyword (for example, "CPU", "memory", or "TCP") to find information items related to that keyword.
A full system overview is available from a single window, making it easy for you to see how well your system is operating. The overview includes information such as the number of servers and agents that are running, the number of servers and agents that have stopped, and the ratio of the first number to the second. You can also view the number of alarms (warnings) that agents generated. From the alarm monitoring window, you can easily determine the statuses of items from the colors of their icons. You can also open reports on monitored information items directly from this window to quickly check details about problems that have occurred.
In addition to monitoring the statuses of servers and processes, you can also monitor the service status of monitoring agents in real time. Even if an agent's operation is suspended, it will automatically restart and resume monitoring. You can specify information retrieved by user applications or by other management tools as well as information specific to the customer's system as items to be monitored.
Events issued from monitored targets can be monitored by multiple manager hosts installed at separate locations, even in non-clustered systems. By having multiple managers monitor the same targets, even if one manager is unavailable due to catastrophic failure, monitoring can continue without interruption.
Create and view reports in a variety of formats, using bar graphs, broken line graphs, lists, tables, and more. You can also overlay graphs of different data types to create hybrid reports, which are useful when, for example, you want to analyze a problem that occurred or to determine correlations and trends emerging from different sets of data.
Your system is continuously accumulating operational data, and managing and making effective use of this ever-increasing volume of data is a constant challenge. JP1 can help by automatically aggregating your data by the minute, hour, day, week, month, or year. This aggregation of data allows you to assess how your system has changed over time, helping to eliminate the reliance on guesswork during capacity planning. In addition, by specifying the amount of time for which aggregated data is to be retained, you can strike a balance between continuous monitoring and the amount of disk space occupied by records.
|Category||Monitoring target||Main types of information that can be monitored|
|Platform (operating system)||Windows||CPU usage, memory usage, disk usage, disk access status, network usage, detailed information for each process, number of processes, device information, service information, event log information, etc.
Information related to Active Directory: number of connected client sessions, number of Windows updates that have not been applied, Active Directory replication traffic, etc.
|Linux, AIX, Solaris, HP-UX||CPU usage, memory usage, disk usage, disk access status, information about the users running each program, process operating status, status of system resources used by each process, amount of data transferred over the network, network usage, network collisions, etc.|
|Virtual environment*||VMware ESXi, Microsoft Hyper-V, KVM, Docker environments (Linux/Windows), Hitachi Compute Blade logical partitioning feature||Rate and amount of CPU usage by physical server or virtual machine; CPU shortage rate; maximum, minimum, and equilibrium values for CPU allocation; amount of used memory; swap space I/O; working set size; working set size ratio; maximum and minimum values for memory allocation; amount of unused memory; amount of allocated memory; amount of used swap space; rate at which disk commands are discarded; usage rate and amount for each logical disk; disk space used by the data store; speeds at which data is sent and received over the network; etc.|
|Database||Oracle Database||CPU usage, memory usage, I/O cache hit ratio, sorting information, detailed information for each process, database usage rate, tablespace information, fragmentation, lock occurrence information, SQL information, error information, parameter information, information about ASM disk groups, etc.|
|Microsoft SQL Server||Status of the space used by the database, cache hit rate, network usage, environment settings information, lock occurrence information, error information, number of scans, number of compilations, physical I/O volume, usage status of transaction logs, job execution statuses, etc.|
|HiRDB||Buffer information (number of actual I/O operations, hit rate, etc.), information about locked resources, network-related information of servers and clients, status of the space used by the database, status of the space used by the HiRDB file system, HiRDB server information, etc.|
|ERP package||SAP ERP, SAP S/4HANA, SAP BW/4HANA||Response time, dispatcher wait time, database request time, number of dialog steps, SAP memory usage rate, SAP buffer hit rate, number of logged-in users, operating statuses of work processes, system log information, CCMS alerts, etc.|
|Other||Other types of performance information||Other types of performance information that can be defined and imported into JP1 for monitoring|
Note: The above table applies to agent-based monitoring. Monitoring targets and the types of information that can be monitored might vary when agentless monitoring is used.