Displaying present location in the site.
MasterScope MISSION CRITICAL OPERATIONS - Technical DetailsEnd-of-life
Centrally manages the messages generated by performance monitoring, application log monitoring, etc. Messages by linkage with the other products are also integrated.
Classifying the messages into each operation items and displaying them in the tree view so that user can identify the business impact immediately in case of any system failure. Enormous messages can be filtered and necessary information is selectively displayed.
Stopping and resuming monitoring can be automatically controlled using the schedule function. This enables to discard the messages and avoid the unnecessary notifications in case of regular system maintenance, for instance.
- Registers the schedule for selected category from the monitoring view
- Batch schedule registration is available by defining a schedule to the category group
Service process monitoring
In addition to alive monitoring of important service/process, MCO monitors from the operation point of view. When incidents occur, it notifies which business will be influenced & affected.
Application log, syslog, and event log monitoring
Monitors the application log, event log and syslog and displays and informs only the necessary information.
In contrast to the conventional system, which only reports what happened in the system, MISSION CRITICAL OPERATIONS (MCO) shows user what should be done during the operation phase.
In order to realize the problem-solving operation management, MCO accumulates past failure information and recovery methods in the knowledge database and shows the countermeasures against failures. Even an inexperienced operator can analyze the situation appropriately and quickly by sharing administrator-level trouble-shooting expertise.
What is knowledge?
Here, knowledge means a guide showing how to recover from failures.
Because the troubleshooting procedure that an experienced operator would perform to handle the failure is shown, an inexperienced operator can perform the same level of troubleshooting, considerably improving the level of administration.
It is also possible to register the system-specific failures as knowledge in case of any reoccurrence.
Alert by flasher, sending e-mail, executing commands (Manager only) in case of server down, etc. Reports can be sent to multiple destinations at the same time.
Network products special order items
(These products are linked with MasterScope MCO report feature)
|Special order number
|Firmware English letters
|Firmware English letters
|NO AC adapter
Also see PATLITE Corporation global website here: http://www.patlite.com/
It graphically displays the performance status (CPU, memory, etc) of each server.
Monitors the capacity of the CPU, memory, etc… Also, generates the message when the threshold is exceeded.
Performance data can be accumulated and charted as statistics.
Regularly collects and displays the server configuration information
File / directories monitoring
This Prevents disk depletion and also enables early detection towards deletion / modification for all the system required files. In case if the file capacity is over and the file deletion, even then sending messages and reports are available. Maximum monitoring capacity is 8 exabytes so this feature can be used for various purposes.
Audit log management
Manages operating status and automatically processes with the help of/by monitoring the terminal/Manager. Each operation and result is recordable as the audit logs for future tracing.
And it is also possible to send a report when certain audit log is being generated.
This feature manages system user information used in the system. Once a user belongs to a group, he/she can perform operations permitted by the rights granted to the group.
User information management
Create and manage system users.
Group information management
Create and manage groups to which users belong and grant rights to groups.
Available rights include the operation right, definition modification right, user management right, and monitor-server-specific reference right.
Controls the on/off of monitoring on defined schedule for each server and message categories.
You can automatically stop monitoring when the server stops at night or during maintenance or automatically start monitoring when the server starts up.
Multiple Agents (including logical system monitor Agents) and monitor terminals can be installed and started on a single server. You can send monitoring data from one server to multiple Managers and monitor/operate multiple Managers from one machine.
Logical system monitoring
Monitors all the statuses of all resources that keep changing in accordance with the cluster package. User can monitor, regardless of the fact that on which host the package is running on.
Monitoring level is the same as usual (performance, alive status, etc). Only the active server can be monitored since the resource on the cluster change is in line with the package.
Logical system agent only supports the active-standby type.
- Monitors the package on the clustered system without being aware of the operation host.
- The icons displayed in the topology view are specific to the logical system.
Event correlation analysis
It analyzes whether a received message meets a specified rule and issues a message that triggers an action to be performed based on the results of the analysis. Event correlation provides the following functions
Generates the other message which is defined as an output event triggered by a specified message.
You can monitor whether a specific message is generated the specified number of times according to the defined condition. This enables you to monitor whether a specific message is frequently generated or not.
Time period condition
This condition is met if another message is received within the specified time from the time when a message is already being generated. For instance, it enables to monitor whether processing is completed within the defined time period from when the processing start/termination message is generated.
Analyzes the occurrence of a specified message and subsequently continues to monitor messages until any message is not generated within a specified time period after the occurrence of the last message.
It does backup monitoring setting while the manager service is running.
- Backup and restoration can be started using a command.
- The Manager service must be stopped during restoration.
Web browser console
The Web browser can be used for monitoring instead of the monitor terminal, which requires installation.
Linkage with the other operation management software
MCO links with related operation management tools and also integrates the information from the other products.
- ESMPRO products (such as ServiceManager, Network Manager, etc)
Linkage features and tools
- Server Agent linkage service
- Operation message notification API
- Event Trap Utility
Scenario control (Option) (MasterScope MISSION CRITICAL OPERATIONS Workflow Manager/Agent)
Automates your daily work by defining a specified workflow. User can also monitor whether the workflow is executed on schedule or not.
By supporting the features specific to scenario control such as business day or non-flow execution, this feature allows for controlling and monitoring of an advanced operation flow.
In particular, non-flow execution enables you to monitor and control not only the fixed operation flow but also an operation flow which can be started/stopped at your convenient timing.
Operation control (Option) (MasterScope MISSION CRITICAL OPERATIONS Operations Manager/Agent)
This feature issues a predetermined action by using the time, generation of a specific message, or an operator's operation as a trigger.
Enables to submit commands to Manager/Agent with a simple step. Avoid forgetting to issue commands by defining a complex command execution as an "operation".
The defined operation can be executed manually by the operator or automatically by using a specific internal event, scheduler, or timer as a trigger. The commands included in the operation can be executed sequentially, in parallel, or on multiple Agents in parallel.
Manager linkage (Option) (MasterScope MISSION CRITICAL OPERATIONS Hierarchical Manager Option)
The whole system can be centrally monitored by linking multiple managers in a hierarchy. Manager of Manager (MOM) collects the messages from Region Manager (RM).
- ※You can specify whether to use linkage for each category in the business view.
Application linkage (Option) (MasterScope MISSION CRITICAL OPERATIONS ApLinker Manager)
Here the text filled message is sent as an output which is collected by MCO to the external applications.
The record format of write-out file can be selected and the user can specify various character encoding (UTF-8, Shift-JIS, etc) to write log files. Log rotation is also made available.
System performance analysis (Option) (MasterScope MISSION CRITICAL OPERATIONS Invariant Analyzer Option)
Automatic analysis is simply realized by input performance data without any professional knowledge or complex setup.
Performance information is automatically acquired in MISSION CRITICAL OPERATIONS and analyzed in real time.
Automatic detection of silent failures
The performance information correlations that does not change during normal operation (invariant) are automatically learned and modeled. An unusual behavior that does not match that model is detected as a silent failure.
Real-time automatic analysis makes it possible to issue a warning message when a failure is detected.
Automation and visualization of analysis and cause determination
You can significantly reduce the time necessary to determine the cause, because the core element of the detected unusual behavior and its extent of impact are intuitively shown in a pie chart or map.
Recording and viewing responses
Responses that have been made can be recorded.
Recorded responses are accumulated and searched for based on similarities with other failures. This helps you reduce the time necessary to respond to any subsequent unusual behavior that is similar.
Description of the basic screen
The simple and easy-to-understand basic screen enables you to see the analysis results at a glance.
Automatic analysis of persistent relationships (invariant)
The system is automatically analyzed using performance information to detect failure occurrence.
- Automatic analysis does not require special knowledge or a complex setup.
- Because the persistent relationships between performance information sets are focused on, it is not necessary to change settings even if the load temporarily fluctuates, such as due to a special advertising campaign.
- Additional analysis can be automatically controlled using an external command.
- Real-time analysis can be performed in MISSION CRITICAL OPERATIONS.
ServiceManager linkage (Option) (MasterScope MISSION CRITICAL OPERATIONS Base Manager ServiceManager Option)
By linking with MasterScope ServiceManager, which is used for IT service management, this feature ensures that all important incidents are addressed and realizes total system IT service management.
*The Manager does not support Windows Server 2008 when the ServiceManager linkage feature is used.
SSC linkage (Option) (MasterScope MISSION CRITICAL OPERATIONS provisioning solution package for Windows)
Linking with NEC SigmaSystemCenter (SSC) enables autonomic provisioning of a three-level system (Web, AP, DB). This feature analyzes failures based on AP failures in Application Navigator or various failure messages by using the invariant analysis feature of MISSION CRITICAL OPERATIONS and gives a provisioning instruction to SSC by using the scenario control feature.
Related products: NEC SigmaSystemCenter, MasterScope Application Navigator
Addition of virtual environment monitoring
The virtual environment monitoring feature realizes central management including conventional integrated monitoring. This feature enables you to model the physical/virtual/logic configuration with CMDB.
For example, components have complex relationships that extend across the physical, logical, and virtual layers in a virtualized environment that has many virtual machines (VMs). Therefore, in the past, it was difficult to identify the extent of impact when a failure occurred.
In contrast, if you use this feature for monitoring, the components and their relationships in the physical, logical, and virtual layers are visually displayed. Therefore, if a failure occurs in a component, its extent of impact can be easily visualized.