# 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. {% hint style="info" %} The VDI Experience license allows extra fine data resolution of VDI metrics at 30-second intervals. See the [#nqltimeselection-timegranularityandretention-1](https://docs.nexthink.com/platform/nexthink-query-language-nql/nql-syntax-overview/nql-time-selection#nqltimeselection-timegranularityandretention-1 "mention") documentation for details. {% endhint %} To access high-resolution data, you must use a timeframe expressed in minutes or hours in the `during past` clause. ```sql 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. ```sql 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](https://docs.nexthink.com/platform/user-guide/administration/content-management/data-management) page. Refer to the [license](https://docs.nexthink.com/platform/user-guide/administration/system-configuration/license "mention") documentation to learn how changing data retention impacts your license count.

Data category	Data subcategory	Retention	Example
Object	Inventory objects	By default, 30 days from the time of the object’s last activity	`devices` `mobile_devices` `users` `binaries` `packages`
Object	Configuration objects	Indefinite, until deleted by a Nexthink account	`campaigns` `remote_actions` `workflows` `monitors`
Events	Operational data	By default, 30 days from the time of the event ℹ️ Exceptions: `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. 30-second high-resolution data for VDI is only retained for the past 48 hours. `agent.conversations` are retained for up to 365 days. You can access a maximum of 90-days data in a single query.	`execution.events` `execution.crashes` `device_performance.events` `device_performance.mobile_events` `remote_action.executions` `workflow.executions` `web.events`
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.
Events	Audit logs	180 days from the time of the event	`platform.audit_logs`
Events	Execution logs	30 days from the time of the event	`platform.custom_trends_logs` `platform.data_export_logs`
Events	Nexthink usage data	90 days from the time of the event	`usage.account_actions`

{% hint style="info" %} The `last_seen` field in the NQL does not account for all the device connections to the Nexthink instance (such as TCP handshakes or remote actions), so it is not a reliable indicator of device retention period. Refer to [NQL data model](https://docs.nexthink.com/platform/nql-data-model#device_device) and [Monitoring device last activity](https://edocs.nexthink.com/nexthink-infinity/infinity-specifications/monitoring-device-last-activity) for more information. {% endhint %} ## 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 | | ----------------------------------- | ------------------------------------------------------------------------------------------ | | Alerts overview | 30 days | | Applications - desktop applications | 14 days | | Applications - web applications |

30 days - operational data

90 days - trend data

2 days - 30-second data resolution
30 days - 5-minute data resolution

30 days - operational data

395 days - trend data

| | Remote Actions |

30 days - operational data

395 days - trend data

30 days (by default) - full conversations
90 days - summarized conversation data

| | Workflows | 30 days | \* The number of hours displayed on the page depends on your screen resolution. {% hint style="info" %} All time-related data displayed in the Nexthink web interface is converted to the user's time zone. {% endhint %} *** RELATED TOPIC * [Data management](https://docs.nexthink.com/platform/user-guide/administration/content-management/data-management)