D.4 Limits when using IM Configuration Management
The tables below describe the limits that apply to JP1/IM - Manager and IM Configuration Management - View when using IM Configuration Management.
- Organization of this subsection
(1) JP1/IM - Manager limits
The following table describes the limits that apply to JP1/IM - Manager.
|
Item |
Limit |
|---|---|
|
Number of instances of JP1/IM - IM Configuration Management - View that can connect to one JP1/IM - Manager |
64 |
|
Number of hosts one JP1/IM - Manager can manage (total number of the JP1/IM - Manager hosts, the JP1/Base instances that can be placed directly below JP1/IM - Manager, and the remotely monitored hosts in the system configuration, regardless of IPv4 hosts, IPv6 hosts, or IPv4/IPv6 hosts) |
2,500 |
|
Number of hosts that can be monitored from one instance of IM Configuration Management (regardless of IPv4 hosts, IPv6 hosts, or IPv4/IPv6 hosts) |
10,000 2,499 agents can be configured directly under IM Configuration Management |
|
Number of tiers in the system hierarchy (IM configuration) that can be monitored by one IM Configuration Management instance |
3 levels (assuming the integrated manager as being in the first level) |
|
Maximum number of files that can be monitored remotely#1 |
1,024 |
|
Maximum number of log file trap processes that can be managed by one host |
100#2 |
|
Number of standby hosts that can be set up on one logical host |
4 |
|
Number of IP addresses that can be displayed for one host |
8 |
|
Total number of business groups and monitoring groups |
100 |
|
Maximum number of hosts that can be set for one business group or one monitoring group |
2,500 |
|
Number of tiers for business groups |
1 level |
|
Number of tiers for monitoring groups |
9 levels |
#1: This is the total of the number of log files monitored by remote log file traps and the number of servers monitored by remote event log traps.
#2: If 101 or more log trap files are active, the message KNAN22411-W is output and the first 100 are collected.
(a) List of limits for using Intelligent Integrated Management Base
The following table describes the limits that apply to JP1/IM - Manager when the Intelligent Integrated Management Base is used.
|
Item |
Limits |
|---|---|
|
Number of events that can be issued in a single API |
100 entries |
|
Length of the message text representing the content of JP1 event. |
1023 bytes |
|
Extended attribute name string length |
32 bytes |
|
Total length of all extended attribute values |
10,000 bytes |
|
Cluster Environment Intelligent Integrated Database setup information file with a string length that can be specified as a Intelligent Integrated Management Database Logical Hostname |
63 bytes |
|
Logical Hostcount of Intelligent Integrated Management Database |
9 |
|
How long to keep your Trend data Management Database |
1096 days |
|
The length of the file path (including the extension) of the distribution |
235 characters |
|
File size of the distribution |
300 megabytes |
(2) JP1/IM - View limits
The following table describes the limits that apply to JP1/IM - View.
|
Item |
Limit |
|---|---|
|
Number of instances of JP1/IM - View that can be started within a single session (per process#1) |
3#2 |
|
Number of definitions that can be specified for a manager host in the non-encryption communication host configuration file for encrypted communication |
1,024 definitions |
|
Maximum length (in characters) of a manager host name in the non-encryption communication host configuration file for encrypted communication |
255 characters |
#1: The following viewers and windows are started for each process:
-
Central Console viewer and Central Scope viewer
-
IM Configuration Management viewer
-
Monitoring Tree (Editing) window
#2: The larger the number of active instances of JP1/IM - View, the greater the memory and disk space requirements.
(3) JP1/IM-Agent Limits List
The following table describes the limits that apply to JP1/IM - Agent.
|
Item |
Limits |
|---|---|
|
Number of monitored objects that can be connected in conjunction with one JP1/IM - Manager#1 |
2,500 |
|
Number of scrapes of one integrated agent#2 |
100 |
|
How many JP1 events for an alert can be fired per minute on a single integrated agent |
150 |
|
How many JP1 events in log trapper can be issued per second on a single integrated agent |
Monitor text log files: 100 Monitor Windows event log: 80 Note IM systems-wide exceeding 200 events per second can cause delays. |
|
Sample amount of performance-data integrated agent can handle per minute |
10,000 |
|
Max concurrent executions of actions that can be performed on integrated agent host |
48 |
|
Maximum #3 of numbers that can be monitored by Fluentd of integrated agent |
- For Windows
- For Linux Monitor text-format log files: 508 files |
- #1
-
JP1/Base,JP1/IM-Agent, user-defined Prometheus and your own Fluentd are covered.
JP1/IM-Agent counts several services/ OSS included in the configuration together as one. Also, JP1/IM-Agent targets (such as Blackbox exporter foreign-shaped targets, Yet another cloudwatch exporter monitored AWS resources, and Fluentd monitored logs) are not counted.
When operating JP1/IM-Agent on physical hosts, logical hosts, and containers, they are counted separately.
- #2
-
Number of scrape targets in Prometheus server per integrated agent host. Prometheus server performs scrape on Exporter in the same host.
The scrape target of the Prometheus server is specified in the item "targets" of the Prometheus configuration file (jpc_prometheus_server.yml).
- #3
-
Do not exceed the limit in JP1 Alerting events-per-minute limit for a single integrated agent.