Maximum supported values with Finder (classic)

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. This is because boundaries of varied nature appear in different contexts within the product.

Below is a comprehensive list of the maximum values within the platform:

  • The number of objects that an Engine instance 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 web interface or to Finder (classic), or both

  • The number of results to obtain from a query, and others.

Respect the limits presented in this document to avoid performance issues.

Objects and events

The table below lists the maximum number of allowed objects and events per Engine.

ObjectDefault maxAbsolute maxConfiguration setting



10 k




As many as linked to devices




As many as installed on devices (repeated packages expected)



40 k

100 k




As many as linked to binaries




As many as linked to binaries




2 x 65​535 (TCP / UDP)




As many as required

A warning is sent when 50k is reached, there is no limit enforced


250 k

250 k



Depends on hardware

200 M


It may be possible to modify the limits on some objects. Contact Nexthink Support for more information.

Lifetime of objects

The lifetime of an object in Nexthink is related to the configured data retention. In 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 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 Engine.

There are three types of objects that are not immediately removed from 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 Engine. Thus, if the maximum inactivity period of an object has not elapsed, the object is not removed from the database, even when there is no event linked to the object left. When 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 equally stored in the database of Engine for as long as a related binary exists. Therefore, the lifetime of applications and executables is determined by the maximum inactivity period of the binaries to which they are related.

ObjectDefault max inactivity periodConfiguration setting


7 776 000 s (90 days)




2 592 000 s (30 days)


The max_inactivity_period and max_binary_inactivity_period settings are configurable. Contact Nexthink Support for more information.

Categories and keywords

There is no fixed maximum number of categories or keywords that can be applied to tag objects. However, a 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:

ItemMaximum recommended values


25 per type of object


800 per category (200 of which with auto-tagging conditions)

Auto-tagging condition

20 per keyword

Collector string tag

When identifying an installation of Collector by means of a string tag, the assigned tag has a maximum of 2048 characters.


There is no fixed limit on the number of services that you can create in Finder. However, the maximum number of simultaneously enabled services is 100.


Service-based alerts

Create a maximum of one alert per service. Therefore, a maximum of 100 service-based alerts are permitted.

Investigation-based alerts

There is no fixed limit on the number of alerts that you can create in 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:

Alert typeMaximum



My alerts + role based



There is no fixed limit on the number of metrics that you can create in Finder. However, there is an actual limit on the number of simultaneously enabled metrics. During the night, Portal computes the values of enabled metrics only.

EnabledDefault max


3 000


There is no fixed limit on the number of scores that you can import into 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.

Limiting factorMax


500 composite or leaf scores (including subscores in the count)

Computation power

200 scores of the Computation input type

The total maximum number of scores is therefore 500 scores, of which a maximum of 50 scores can be of the Computation input type. These are not absolute maximums and can be exceeded by contacting Nexthink Support.

The Digital Experience Score is embedded in the product. The scores that compose the Digital Experience Score are therefore regarded as part of the base product, such that they consume no part of the maximum number of scores available for the customer.

Engage and Act

The Engage and Act products 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 ofComputationMaximum


  • 3 fixed + 1 per question + 1 per optional text

  • 0, if embedded in a remote action


Remote action

6 fixed + 1 per output


Because of performance reasons, there is also an additional limit on the number of campaigns and remote actions that can be simultaneously enabled. Regarding campaigns, note that the limit on the usable custom fields may be more restrictive than the limit on the number of campaigns themselves. In the case of remote actions, the limit affects only automatically triggered remote actions and the number depends on the frequency of the action.



  • 15 one-off or recurring campaigns

  • 15 continuous satisfaction measurement campaigns

  • 100 manual campaigns

  • 1000 embedded (in remote actions) campaigns

Remote action

  • 60 automatically triggered

  • 30 out of the previous 60 with period < 1 hour

  • 10 out of the previous 30 with period = 1 min

Portal content

The maximum number of modules, dashboards and widgets is not specified.

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, but they are known to be higher than the following values:

ItemsMaximum value


> 300


> 400

Similarly, there is no specified limit on the number of hierarchies and levels that can be created, as long as they do not exceed the maximum supported complexity in Portal. Contact Nexthink Support for more information.

The maximum length of the names that you can specify for user accounts, profiles and roles is as follows:

ItemsMaximum number of characters


128 characters


256 characters


25 characters

The password length of internally managed accounts (that is, not provisioned from SAML or Active Directory) has the following limits:

ItemMinimum number of charactersMaximum number of characters


8 characters

25 characters

The minimum number of characters can be changed. Contact Nexthink Support for more information.

Entities and nodes

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.

The maximum length for the names of entities and nodes is 50 characters.

ItemsMaximum number of characters


50 characters


50 characters

Finder (classic)


There is no specified limit on the number of investigations that can be created in Finder. Related to investigations, the maximum number of results shown by a cross-Engine investigation is 10'000 entries (this can be overcome by exporting the results of the investigation).

The maximum query time of an investigation is 900 seconds (15 minutes). After that, 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 is 10'000 connections or requests per view.

Last updated