Skip to main content
Intelligent Monitoring | Infrastructure management
Need to optimize the management and operation of an IT infrastructure that has been consolidated via the use of virtual environments and cloud technology?
JP1/Operations Analytics improves and optimizes tasks related to managing and operating an IT infrastructure that has been consolidated via the use of virtual environments and cloud technology.
IT systems are becoming increasingly complex as virtual environments and cloud services are introduced in an effort to reduce costs. To manage such systems, administrators must be knowledgeable about the various applications and devices they manage, and must possess the skills required to handle any failures that might occur.
JP1/Operations Analytics can be used to automatically collect information about the servers, switches, storage systems, and other IT infrastructure components used by your business systems. Based on this information, JP1 identifies and graphically displays relationships between these components and the applications you use. You can also use JP1/Operations Analytics to create reports on the operating statuses of your systems, as well as useful reference materials to be used when you want to change the allocation of resources.
Based on the configuration of the IT infrastructure and the relationships between IT infrastructure components and business systems, you can identify not only the location of a failure, but also the components where failures are likely to occur next and the business systems that might be affected. With this information, you can promptly notify the relevant persons.
Furthermore, you can easily find the information you need to identify the cause of a failure, allowing you to perform investigation work (which previously required high-level skills and expertise) with greater efficiency. JP1/Operations Analytics also suggests ways to resolve bottlenecks and indicates the likelihood of success, helping you decide on the best form of action and significantly reducing the time to recovery.
Even as IT systems become increasingly complex with the introduction of virtual environments and cloud services, JP1/Operations Analytics can be used to automatically collect information about the applications, servers, switches, storage systems, databases, and other components used by your business systems. Based on the collected information, JP1 analyzes the connections between components, and then identifies and graphically displays the relationships between application-related events and the operating statuses of components of the IT infrastructure. Specifically, for each business system, you can check which servers, switches, and storage systems are connected to that business system, as well as which applications (and the hosts running those applications) are used by that business system. Understanding these relationships helps you understand the configuration of the entire system.
JP1's assisted report creation content#1 allows you to output collected configuration information and performance information, making it easy to create reports on the system's operating status and reports to be used when you want to re-examine the allocation of resources.
To help you get an overview of the system status, JP1/Operations Analytics provides various types of information about business systems, categorized by importance, all in one place. From the dashboard, you can determine whether an error has occurred, check the number and content of warnings that have been issued for servers and storage systems, check the statuses of system resources, and identify trends in the events occurring in the system. By monitoring the statuses of failures both in terms of the IT system as a whole and in terms of business systems, you can better assess the severity of failures and determine the appropriate order in which to address the failures. Users can customize their own dashboard by selecting, from a multitude of report widgets, those that they are interested in and then arranging those widgets on the dashboard in a way that best suits their purposes.
Icons alert you to components that have failed or for which warnings have been issued. When you select such a component, the servers and other devices that are connected to that component are highlighted, making it easy to determine whether one problem is related to another. For example, if multiple virtual machines that share a common resource fail, you might suspect that the problem is caused by competition over the shared resource. To verify this hypothesis, you can click the resource in question. If all of the virtual machines that failed are highlighted, there is a good chance that the shared resource is causing a bottleneck.
Similarly, by checking graphically displayed information about the applications used in your system, when multiple events occur (such as a delay in job execution, database cache insufficiency, or a large number of server I/O operations), you can determine whether the events are related.
When a resource is believed to be causing a bottleneck, you can checking a list of the business systems or servers that use that resource allows you identify (in addition to business systems where failures have already occurred) business systems where failures are like to occur next. As the next step, you can promptly notify the relevant persons using the registered contact information and other information associated with each business system.
With JP1, you can easily find the information you need to identify the cause of a failure, allowing you to perform investigation work (which previously required high-level skills and expertise) with greater efficiency.
When a failure occurs, JP1/Operations Analytics makes it easy to recognize relationships between applications and IT infrastructure resources. By viewing a timeline of JP1 events (events managed by JP1/Integrated Management 2) for a particular application, you can easily check how many of each type of event has occurred for that application. You can then select an event to view a performance graph of related resources and identify, at a glance, any resources whose performance degraded around the time the event occurred.
For a resource believed to be causing a bottleneck, you can view the performance data of that resource alongside the performance data of a resource that failed. By comparing the changes and trends in the data, you can identify potential correlations. By repeating this process for different resources, you can narrow down the list of resources that might be causing the bottleneck until you pin down the actual resource behind the bottleneck.
Once a resource is identified as the cause of a bottleneck, JP1/Operations Analytics automatically displays the performance data of that resource and that of "noisy neighbors" (other resources that might be affecting the bottleneck). Based on this information, you can easily investigate the various factors leading up to the bottleneck.
Sometimes, failures are caused by changes in the system configuration. To determine whether a particular failure is the result of a configuration change, you can view the performance data of the resource causing the bottleneck graphed along the same time axis as information about system configuration changes. For example, using the graphs above, you can visually determine whether a sharp increase in the CPU usage of a physical server was caused a configuration change (such as the addition or migration of virtual machines right before the increase).
By analyzing resources related to the component that failed, JP1/Operations Analytics automatically identifies resources that are strongly correlated, in terms of operating performance, to the component that failed. Information about the resources most likely to be the cause of the failure is then displayed both in graphs and as numerical data for easy understanding.
JP1/Operations Analytics suggests different ways to resolve a failure based on the operating status of the resource causing the bottleneck, when the failure occurred, and the target performance values to be achieved after recovery. For each suggestion, JP1 indicates the likelihood that the suggestion will successfully resolve the failure as well as the side effects that might occur. With this information, you can more confidently decide on the best form of action and significantly reduce the time to recovery.
With JP1, you can define actions related to recovery work, such as sending procedures via email and issuing a problem management ticket. By defining these actions in advance, when a problem actually occurs, you can easily and confidently carry out the necessary recovery work. For example, when JP1/Operations Analytics is linked with JP1/Navigation Platform (a product for visualizing work procedures), procedures for the necessary recovery work are sent to operators, who then carry out the work simply by following the provided instructions and flowcharts. With these procedures, recovery no longer depends on the skills and expertise of individual operators.
Problems that require more time to resolve can be registered in JP1/Service Support, a product that helps you manage inquiries and incidents (including failures). When you register a problem, a problem management ticket is issued, which you can use to keep track of the problem's status and the progress of the work being done to resolve to problem. This helps ensure that no problem is overlooked and that all problems are resolved in a timely manner.