D.1 Limits when using the Central Console

The tables below describe the limits that apply to JP1/IM - Manager and JP1/IM - View when using the Central Console. The Web-based JP1/IM - View, as a feature of JP1/IM - Manager (JP1/IM - Central Console), is subject to the JP1/IM - Manager limits.

Organization of this subsection

(1) JP1/IM - Manager limits
(2) JP1/IM - View limits

(1) JP1/IM - Manager limits

The following table describes the limits that apply to JP1/IM - Manager and the Web-based JP1/IM - View.

Table D‒1: Limits for JP1/IM - Manager
Item	Limit
Number of instances of JP1/IM - View that can connect to one JP1/IM - Manager	64
Number of instances of the Web-based JP1/IM - View that can run on one machine	1
Number of hosts that can be managed by one instance of JP1/IM - Manager (JP1/Base hosts that can be placed directly below JP1/IM - Manager, regardless of IPv4 hosts, IPv6 hosts, or IPv4/IPv6 hosts)	1,024 When `close` is specified as the communication type in the event server settings file (`conf`) of JP1/Base on the manager 100 (UNIX); 62 (Windows) When a value other than `close` is specified as the communication type in the event server settings file (`conf`) of JP1/Base on the manager This value is for a maximum configuration. The number of managed hosts is restricted by the system configuration and network traffic.
Number of hosts that can execute commands from one instance of JP1/IM - Manager	1,024 When the managed hosts include a host running JP1/Base 06-51 or earlier, a maximum of 60 such hosts can be configured directly under JP1/IM - Manager. In this case, the maximum number of hosts that can execute commands concurrently from one JP1/IM - Manager is 60 (in Windows) or equal to the number of file descriptors^#1 that can be used in one process minus 10 (in UNIX). The calculation here assumes that a host running JP1/Base 06-51 or earlier under JP1/IM - Manager is executing commands even if it is not doing so in reality.
Event buffer size (number of extracted events that can be buffered from the event database)	2,000
Scroll buffer size (number of events that can be displayed in a window) in the Web-based JP1/IM - View	1,000
Number of events that can be acquired when a window is refreshed in the Web-based JP1/IM - View	200
Number of events that can be acquired in a search in the Web-based JP1/IM - View	1,000
Maximum length of an event acquisition filter^#2 (total size of the event acquisition filters to be applied (total of pass conditions and exclusion-conditions) and the valid common exclusion-condition groups)	60 KB When an exclusion-condition group or a valid common exclusion-condition group is not set. 64 KB When an exclusion-condition group or a valid common exclusion-condition group is set.
Maximum length of an event receiver filter^#2	1 MB (total size when more than one event receiver filter is set)
Maximum length of a severe events filter^#2	64 KB
Maximum length of a view filter^#2	1 MB per JP1 user (total size when more than one view filter is set)^#3
Maximum length of an event search^#2	64 KB (when connected to JP1/Base 06-51 or later; 4 KB when connected to JP1/Base 06-00)^#3
Number of event receiver filters	128
Number of conditions that can be set in a filter (applies to passing conditions and exclusion-conditions)	Event acquisition filter: 30 per filter Event receiver filter: 30 per filter Severe events filter: 30 View filter: 5 per filter Event search: 5
Maximum length that can be entered in the input field of an item for which multiple attribute values can be specified in a filter window^#4 of the Web-based JP1/IM - View	30,000 bytes
Number of filters that can be defined in the list of event acquisition filters	50
Maximum length of a filter name specified in the list of event acquisition filters	50 bytes
Number of common exclusion-conditions that can be defined in the list of event acquisition filters	30
Maximum size of the file containing the list of event acquisition filters	1 MB
Number of queued commands executed by automated actions	65,535 When the target host on which the automated actions are to be executed is running JP1/Base 06-71 or later 64 When the target host on which the automated actions are to be executed is running JP1/Base 06-51 or earlier
Length of an action definition parameter for an automated action	No limits when using version 09-00 or later. However, the following items specified in an action definition parameter have limit values: Length of an action name: 1 to 50 bytes Length of a comment: 1,040 bytes Length of an event condition: 4,096 bytes Length of a user name: 31 bytes Length of `executing-host-name` `\|` `host-group-name`: 255 bytes Length of a `business-group-name` `\|` `monitoring-group-name`: 2,048 bytes Length of an action: 4,096 bytes Length of an environment variable file name: 255 bytes Size of an automated action definition file: 22 megabytes (23,068,672 bytes)
	When version 08-50 or earlier is used: 5,706 bytes However, the following items specified in an action definition parameter have limit values: Length of an event monitoring condition: 1,040 bytes Length of an action: 4,096 bytes Length of the user name for executing an action: 31 bytes Length of an environment variable file name: 255 bytes Length of a target host name: 255 bytes
File size of a severity changing definition file	17 MB (17,825,792 bytes)
Length of a target group name	30 bytes
File size of an event guide information file	1 MB
File size of an event-guide message file	1 MB
Total number of items that can be defined in an event guide information file	1,000
Length of an event-guide message after processing of placeholders (variables) and HTML encoding	196,608 characters^#5
Length of an event guide-message file name that can be specified in an event guide information file	1,024 characters^#5
Number of comparison conditions that can be defined in event guide information	100
Number of correlation event generation conditions that can be defined in a correlation event generation definition file	1,000
Number of filtering conditions for the correlation target range that can be defined in one correlation event generation condition	1
Number of event conditions that can be defined in one correlation event generation condition	10
Timeout period for a correlation event generation condition	1 second to 86,400 seconds (24 hours)
Maximum value that can be specified in the threshold event correlation type	100 events
Number of duplicate attribute value conditions that can be defined in one correlation event generation condition	3
Number of maximum correlation numbers that can be defined in one correlation event generation condition	1
Maximum length of the attribute value used in defining a correlation approval event	2,048 bytes
Number of sets of JP1 events that can be correlated simultaneously by one correlation event generation condition	1,024 sets
Number of sets of JP1 events that can be correlated simultaneously by all correlation event generation conditions	20,000 sets
Health check timeout period	216,000 seconds (60 hours)
Number of characters that can be specified for a URL in IE	2,046 characters
Number of conditions that can be defined in the List of Repeated Event Conditions window	1,024
Total size of the definitions of repeated event conditions	10 megabytes (10,485,760 bytes)
Length of a definition of repeated event condition	No limits However, the following items specified for a repeated event condition have limit values: Repeated event condition name: 1 to 50 bytes Comment: 0 to 1,024 bytes Event conditions: 0 to 256 conditions Operand of event condition: 65,536 bytes^#6 Conditions for same attribute values: 0 to 3 conditions Number of seconds as threshold: 1 to 60 Number of events as threshold: 1 to 200 End monitoring period: 1 to 86,400 seconds Time for Checks for suppression to continue: 1 to 86,400 seconds Number of events for Checks for suppression to continue: 1 to 1,000,000
Maximum number of email destinations that can be specified at a time by the email notification function of JP1/IM - Manager	20 Multiple destinations cannot be specified over the maximum length of the command line.
Maximum lengths of items with which mail can be sent by the email notification function of JP1/IM - Manager	Mail address: 256 bytes Mail subject: 512 bytes Mail text: 4,096 bytes One line of mail text: 512 bytes
Number of days that can be specified as the range of events to be collected at login	1 to 31 days
Base time that can be specified for the range of events to be collected at login	0:00 to 23:59
Time that can be specified as the range of events to be collected at login	1 to 744 hours (corresponding to 31 days)
Number of definitions that can be defined by the severity changing definition function	1,000

#1: The number of file descriptors available to one process is system-dependent.

#2: Because the character string data is stored in Shift-JIS code, the specifiable length of the character string is the same even if JP1/IM - Manager is running in Japanese UTF-8 code.

#3: This limit applies to the Web-based JP1/IM - View.

#4: Filter windows are the Severe Event Definitions window, Event Search Conditions window, Settings for View Filter window, and Detailed Settings for Event Receiver Filter window.

#5: Both 1-byte and 2-byte characters are counted as one character. For example, "AAA" is counted as three characters.

#6: For details about the limits other than the size of the operand of the event condition, see 3.4.3(2) Event comparison attributes that can be specified in repeated event conditions.

To Page Top

(2) JP1/IM - View limits

The following table describes the limits that apply to JP1/IM - View.

Table D‒2: Limits for JP1/IM - View
Item	Limit
Number of concurrent logins from one instance of JP1/IM - View	3^#1
Scroll buffer size (number of events that can be displayed in a window)	2,000
Number of events that can be acquired when a window is refreshed	200
Number of events that can be acquired in a search	2,000
Maximum length of a filter^#2	View filter: 1 MB per JP1 user (total size when more than one view filter is set) Event search: 64 KB (when connected to JP1/Base 06-51 or later; 4 KB when connected to JP1/Base 06-00)
Number of view filters	50
Maximum length of a name of a view filter	50 bytes
Number of condition groups that can be set in a filter (applies to passing conditions and exclusion-conditions)	Event acquisition filter: 30 per filter Event receiver filter: 30 per filter Severe events filter: 30 View filter: 5 per filter Event search: 5
Maximum length that can be entered in the input field of an item for which multiple attribute values can be specified in a filter window^#3	30,000 bytes
Number of filters that can be defined in the list of event acquisition filters	50 (When connected to JP1/IM - Central Console 08-00 or later)
Number of common exclusion-condition groups that can be defined in the list of event acquisition filters	30
Longest environment variable file name that can be specified in the Execute Command window^#4	255 bytes
Longest target host name that can be specified in the Execute Command window	255 bytes
Longest action definition parameter for an automated action definition	When connected to JP1/IM - Manager 09-00 or later: No limits when using version 09-00 or later. However, the following items specified in an action definition parameter have limit values: Length of an action name: 1 to 50 bytes Length of a comment: 1,040 bytes Length of an event condition: 4,096 bytes Length of a user name: 31 bytes Length of `executing-host-name` `\|` `host-group-name`: 255 bytes Length of a `business-group-name` `\|` `monitoring-group-name`: 2,048 bytes Length of an action: 4,096 bytes Length of an environment variable file name: 255 bytes When version 08-50 or earlier is used: 5,706 bytes The following limits apply to the individual items specified in the action definition parameter: Length of an event monitoring condition: 1,040 bytes Length of an action: 4,096 bytes Length of the user name for executing an action: 31 bytes Length of an environment variable file name: 255 bytes Length of a target host name: 255 bytes
	When connecting to JP1/IM - Manager version 08-00 to 08-50: 5,706 bytes The following limits apply to the individual items specified in the action definition parameter: Length of an event monitoring condition: 1,040 bytes Length of an action: 4,096 bytes Length of the user name for executing an action: 31 bytes Length of an environment variable file name: 255 bytes
Number of lines of execution results to display in the Execute Command window that can be specified in the Preferences window	100 to 10,000 lines
Size of text data that can be copied to the clipboard	6 MB
Number of conditions that can be defined in the List of Repeated Event Conditions window	1,024
Total size of the definitions of repeated event conditions	10 megabytes (10,485,760 bytes)
Length of a definition of repeated event condition	No limits However, the following items specified for a repeated event condition have limit values: Repeated event condition name: 1 to 50 bytes Comment: 0 to 1,024 bytes Event conditions: 0 to 256 conditions Operand of event condition: 65,536 bytes^#5 Conditions for same attribute values: 0 to 3 conditions Number of seconds as threshold: 1 to 60 Number of events as threshold: 1 to 200 End monitoring period: 1 to 86,400 seconds
Number of days that can be specified as the range of events to be collected at login	1 to 31
Base time that can be specified for the range of events to be collected at login	0:00 to 23:59
Time that can be specified as the range of events to be collected at login	1 to 744 hours (corresponding to 31 days)
Number of definitions that can be defined by the severity changing definition function	1,000

#1: The larger the number of concurrent logins, the greater the memory and disk space requirements.

#2: Because character string data is stored in Shift-JIS code, the specifiable length of a character string is the same even if JP1/IM - Manager is running in Japanese UTF-8 code.

#3: Filter windows are the Severe Event Definitions window, Event Search Conditions window, Settings for View Filter window, and Detailed Settings for Event Receiver Filter window.

#4: The total size of all fields must be no more than 2,305 bytes (For example, if five conditions are set, the total size of the five attribute values must be no more than 2,305 bytes).

#5: For details about the limits other than the size of the operand of the event condition, see 3.4.3(2) Event comparison attributes that can be specified in repeated event conditions.

To Page Top