Skip to main content
Skip table of contents

Data resolution and retention

Event data resolution

To allow for more efficient troubleshooting, metrics in operational data are available with high resolution, either 5-minute or 15-minute, and low resolution, 1-day.

To access high-resolution data, you must use a timeframe expressed in minutes or hours in the during past clause.

CODE
devices during past 24h
| include session.events during past 24h 
| compute total_user_interaction = user_interaction_time.sum() 
| where total_user_interaction > 8h
| list device.name, total_user_interaction 

To access data in low-resolution, you must use a timeframe expressed in days in the during past clause.

CODE
devices during past 30d
| include session.events during past 30d 
| compute total_user_interaction = user_interaction_time.sum() 
| where total_user_interaction > 10d
| list device.name, total_user_interaction 

Contrary to metrics in operational data, trend data metrics are available only with low resolution, either 1-day or 7-days.

Retention per data category

Data retention refers to the period of time for which the specific set of data is stored and accessible through dashboards and investigations. The following table summarizes the general rules of retention per data category. The retention periods represent the default platform settings. You can customize them on the Data management (GDPR) page.

Data categories

Retention

Examples

Objects

Inventory objects

30 days from the time of the object’s last activity

devices

users

binaries

packages

Configuration objects

Indefinite, until deleted by a Nexthink account

campaigns

remote_actions

workflows

monitors

Events

Operational data

30 days from the time of the event

Exception:

execution.events, connection.events, connection.tcp_events and connection.udp_events at high resolution are retained for 14 days. Additionally, you can only access a maximum of 8-days data in a single query.

execution.events

execution.crashes 

device_performance.events

remote_action.executions 

workflow.executions

web.events

Trend data

Ranging from 90 days to 13 months, depending on the use case

  • Software metering: 90 days

  • Web applications trends: 90 days

  • Remote action execution summaries: 13 months

  • Workflow execution summaries: 13 months

  • Custom trends: 13 months

  • DEX trends : 13 months

Exception:

Campaigns data (campaign.*) is stored indefinitely.

custom_trend.*

software_metering.events 

remote_action.executions_summary

workflow.executions_summary 

Web applications and DEX trends are not available in NQL, they are only available in the related module dashboards.

Audit logs

180 days from the time of the event

platform.audit_logs

Data availability in modules

Product modules allow you to access the object and event data described above. The available data value indicates how far back in the past you can retrieve the data for a given module.

Module

Available data

Digital Experience

395 days

Alerts overview

30 days

Diagnostic view

14 days

Device View

30 days*

Applications - web applications

30 days - operational data

90 days - trend data

Applications - desktop applications

14 days

Live Dashboards

30 days - operational data

395 days - trend data

Remote Actions

30 days - operational data

395 days - trend data

Campaigns

10 years

Software Metering

90 days

Workflows

30 days

* The number of hours displayed on the page depends on your screen resolution.


RELATED TOPIC

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.