_NGA

The _NGA data point is structured as follows:

Element Name Type Default Description
diskCapacityInBytes long 0 Limit disk usage of disk buffers (size).
requestLicense bool false Setting this element triggers a licence check on all backends and archive groups.
limitDiskCapacity bool false Limit disk usage of disk buffers (on/off).
monitor struct -
bufferDiskSpaceUsed long - Disk space used for buffering (in MBytes).
limitAlertQuerySize int 1.000.000

Defines how many maximum data-rows (independent of the number of the columns) are allowed in a non-split alarm (alertGet, alertGetPerdiod, dpQuery) query.

A value of zero disables the limiting. If a query is bigger than the set limit, the query is aborted.

To further reduce load on the database, each query has now an implicit limit of the configured limit+1. Therefore, the frontend knows if too many rows are returned and shows an error message. The limit clause in dpQuery ca not be used to override this limit.

For split messages the split size effectively makes single answers small enough. Therefore, this limit does not apply to them.
limitEventQuerySize int 2.000.000

Defines how many maximum data-rows (independent of the number of the columns) are allowed in an non-split event (dpQuery, dpGetPeriod, dpGetAsynch) query.

A value of zero disables the limiting. If a query is bigger than the set limit, the query is aborted.

To further reduce load on the database, each query has now an implicit limit of the configured limit+1. Therefore, the frontend knows if too many rows are returned and shows an error message. The limit clause in dpQuery cannot be used to override this limit.

For split messages the split size effectively makes single answers small enough. Therefore, this limit does not apply to them.