Maximum supported values
Maximum supported values
To guarantee the correct operation of Nexthink at an adequate level of performance, certain elements and aspects of a setup must be kept below their maximum values, as boundaries of varied nature appear in different contexts within the product.
As a reference, find below a comprehensive list of the maximum values within the platform: the number of objects that an Engine can store; the alerts, services, metrics or actions that can be simultaneously enabled; the hierarchies and the levels that organize your groups of devices; the accounts, profiles and roles that grant access either to the Portal or to the Finder, or to both; the number of results to obtain from a query; etc.
Respect the limits presented in this document to avoid unsupported scenarios.
Objects and events
Find below the maximum number of allowed objects and events per Engine:
|Object||Default max||Absolute max||Configuration setting|
|User||-||As many as linked to devices||-|
|Package||-||No limit specified (packages repeated in devices expected)||-|
|Binary||40 k||100 k||max_binaries|
|Executable||-||As many as linked to binaries||-|
|Application||-||As many as linked to binaries||-|
|Port||-||2 x 65535 (TCP / UDP)||-|
|Destination||50 k||200 k||destinations_count_alert (only a warning, limit not enforced)|
|Domain||250 k||500 k||hard_max_domains|
|Printer||-||No limit specified (fewer printers than devices expected)||-|
|Event||50 M||400 M||max_events|
Modify the limits on objects that allow it by changing the corresponding setting in the configuration file of the Engine. Contact Nexthink Support before modifying the default values:
Prefer the Web Console to modify the maximum number of events.
In multi-Engine environments, a single Nexthink setup supports all the objects and events held by every Engine that is part of the setup, with the only limit on the total number of devices:
- For setups with more than 150 k devices, contact Customer Success Services to guide you with the deployment, validate your installation and obtain support.
Lifetime of objects
The lifetime of an object in Nexthink is related to the configured data retention. In the Portal, the metrics computed can extend their lifetime to several years, and the details of count metrics last for as long as there is free disk space allocated for them. As for the Engine, an object is kept in its database until all the events that are linked to that particular object have disappeared from the history of the Engine.
Three types of objects are however not immediately removed from the Engine after losing all their linked events: devices, users and binaries. These objects have an associated maximum inactivity period that may go beyond the history of events in the Engine. Thus, if the maximum inactivity period of an object has not elapsed, the object is not removed from the database of the Engine, even when there is no event linked to the object left. When the Engine records new activity for a device, a user or a binary, the inactivity period associated to the object is reset.
Because application and executable objects are linked to binaries, they are also kept in the database of the Enging for as long as a related binary exists. Therefore, by transitiveness, the lifetime of applications and executables is determined by the maximum inactivity period of the binaries to which they are related.
|Object||Default max inactivity period||Configuration setting|
|Device||7 776 000 s (90 days)||max_inactivity_period|
|Binary||2 592 000 s (30 days)||max_binary_inactivity_period|
Modify the max_inactivity_period and max_binary_inactivity_period settings in the configuration file of the Engine. Contact Nexthink Support before modifying the default values:
Categories and keywords
There is no fixed maximum number of categories or keywords that can be applied to tag objects. However, a great number of categories or keywords, especially keywords that specify auto-tagging conditions, may have an impact on the overall performance of a Nexthink setup. Thus, the maximum recommended values to keep your system under an acceptable level of performance are the following:
|Item||Maximum recommended values|
|Category||25 per type of object (device, user, etc.)|
|Keyword||800 per category (200 of which with auto-tagging conditions)|
|Auto-tagging condition||20 per keyword|
There is no fixed limit on the number of services that you can create in the Finder. However, the maximum number of simultaneously enabled services is 100.
Create a maximum of one alert per service. Therefore, a maximum of 100 service-based alerts are permitted.
There is no fixed limit on the number of alerts that you can create in the Finder. However, the total number of enabled investigation-based alerts per Engine cannot exceed 150 alerts, including global and user specific alerts. The distribution between global and user specific alerts is as follows:
|My alerts + role based||10|
There is no fixed limit on the number of metrics that you can create in the Finder. However, there is an actual limit on the number of simultaneously enabled metrics. During the night, the Portal computes the values of enabled metrics only.
|Enabled||Default max||Absolute max|
There is no fixed limit on the number of scores that you can import into the Finder. However, there is an actual limit on the number of simultaneously enabled scores. The maximum number of enabled scores is limited by two factors: storage and computation power required.
|Storage||150 composite or leaf scores (including subscores in the count)|
|Computation power||50 scores of the Computation input type|
The total maximum number of scores is therefore 150 scores, of which a maximum of 50 scores can be of the Computation input type. These are not absolute maximums though. Contact Customer Success Services if you need to exceed these limits.
Engage and Act
The Engage and Act modules store information on the user and device objects, respectively, by means of custom fields; that is, properties or attributes that are dynamically added to the data model of the object. For instance, a user object stores the answer of the user to a campaign in a dedicated custom field; whereas a device object stores the execution status of a remote action on another custom field. There is a limit on the total number of custom fields that campaigns and remote actions can add to the system.
|Custom fields of||Computation||Maximum|
|Campaign||3 fixed + 1 per question||150|
|Remote action||6 fixed + 1 per output||500|
Because of performance reasons, there is also an additional limit on the number of campaigns and remote actions that can be simultaneously enabled. In the case of remote actions, the limit affects only automatically triggered remote actions and the number depends on the frequency of the action.
The maximum number of modules, dashboards and widgets is not specified and mostly dependent on the memory available in the Portal.
Accounts and hierarchies
The maximum number of user accounts supported by a Nexthink setup is 500 users. There is no specified limit on the maximum number of profiles and roles associated to the user accounts.
Similarly, there is no specified limit on the number of hierarchies and levels that can be created, for as long as they do not exceed the maximum supported complexity in the Portal.
The maximum total number of entities in a Nexthink setup is 8 000 entities, which can be distributed among Engines with a maximum of 500 entities per Engine.
The maximum number of rules that can be specified in the CSV file to define entities is 1 000 rules per entity.
There is no specified limit in the number of investigations that can be created on the Finder. Related to investigations, the maximum number of results shown by a cross-Engine investigation is 10 000 entries (can be overcome by exporting the results of the investigation).
The maximum query time of an investigation is 900 s (15 min). After that, the Engine aborts the query.
Network and Web activity views
The maximum number of connections or web requests that can be visualized in the Network and Web activity views are 10 000 connections or requests per view.
- Increasing the maximum number of metrics
- Maximum number of remote actions
- Limit on the number of scores
- Maximum number of published campaigns
- Limit on the number of alerts
- Maximum number of users
- Maximum number of binaries
- Domain replacement
- Setting the maximum number of events
- Limit on the number of rules per entity
- Maximum entities per Engine
- Maximum entities per Portal and complexity