D.1 Limits when using the Intelligent Integrated Management Base

The following table describes the limits that apply to JP1/IM - Manager and JP1/IM - Agent when the Intelligent Integrated Management Base is used.

Table D‒1: Limits for JP1/IM - Manager (Intelligent Integrated Management Base)
Item	Limit
Number of the integrated operation viewers that can connect to one JP1/IM - Manager (Intelligent Integrated Management Base)	64
Number of management nodes that are managed by JP1/IM - Manager (Intelligent Integrated Management Base)	150,000
Number of layers that are viewable between `All` `Systems` and subsystems	10
Number of levels that are viewable under a job group in the tree	30
Total number of layers that are viewable in the tree	45
Number of levels that are viewable in the preceding node of the center node for a root jobnet	2
Number of levels that are viewable in the following node of the center node for a root jobnet	2
Number of bytes of a node name for a root jobnet	40 bytes
Number of nodes that are viewable at one layer of a root jobnet	1,000
Total number of lines for relations in a root jobnet	10,000
Number of bytes that are viewable as a related node name	40 bytes
Number of related nodes per node	1,000 nodes
Total number of lines that can be displayed as relation lines of related nodes	10,000
Number of custom UIs that can be displayed for one IM management node	10
Number of charts that can be displayed in trend information	10
Number of instances per chart in trend information	10
Number of data items (plots) per instance in trend information	60
Number of suggestion definitions	1,000
Number of suggestion activation criteria that can be defined per suggestion definition	100
Number of response actions that can be defined per suggestion definition	1
Number of JP1 permission levels that can be defined per suggestion definition	100
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 Management 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
Maximum number of dashboards that can be defined	30,000 pieces
Maximum number of characters that can be defined for a dashboard name	255 characters
Maximum number of characters that can be defined for a panel name	255 characters
Extensions that can be specified in the background image of the dashboard	PNG only
Maximum number of digits that can be specified with "Sort" specified with Dashboard management	1 to 9999999
Maximum size of the background image that can be specified in the dashboard	4 megabytes

Table D‒2: Limits for 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 Monitor text-format log files: 508 files Monitor Windows event log: 508 types - 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 a scrape on an Exporter in the same host or on an Exporter in another 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.

To Page Top