Data Retention Definitions and Policies

Definitions

A managed resource is considered inactive if it meets all of the following criteria for 90 consecutive days or longer.
- No metrics are collected.
- No events are collected.
- No consoles are launched.
- No jobs, scripts, patches, or anti-virus updates are applied.
An active device is one that does not meet the above criteria.

A client is considered inactive if they meet one of the following criteria for 90 consecutive days or longer.
- A client has no active devices.
- A client is marked as inactive within OpsRamp.
An active client is one that does not meet the above criteria.

A partner is considered inactive if they meet one of the following criteria for 90 consecutive days or longer.
- Partner has no active clients.
- Partner is explicitly marked as inactive within OpsRamp.
An active partner is one that does not meet the above criteria.

A user is considered inactive if they meet the below criteria for 90 consecutive days or longer.
- The user’s OpsRamp account is deactivated.
- The user’s OpsRamp account is terminated.
An active user is one that does not meet the above criteria.

Deleted data is no longer visible and cannot be restored.

The following table specifies the data type and retention policy.

Data Retention Criteria
Data Type	Criteria	Retention
Resources	Inactive resources	90 days
Partners	Inactive partners	90 days
Clients	Inactive clients	90 days
Tickets	Closed tickets	12 months
Tickets	Open tickets	As long as the ticket is open.
Metrics	Metrics collected from managed environment.	12 months
Alerts	Suppressed and closed	90 days
Alerts	Open alerts	As long as the alert is open.
Graphs	Graphs with no data.	15 days
Reports	Recurring reports	Last 5 generated reports.
Reports	One-time reports	90 days
Jobs Scripts, and Patch activity	Jobs results	90 days
Jobs Scripts, and Patch activity	Custom script	90 days
Patches	Missing patches, once detected but not re-detected for 180 consecutive days or longer.	90 days
Secure Console Recordings	Rolling history of console recording for each resource.	90 days

Deleted data is no longer visible and cannot be restored.

January 1: A device is onboarded in OpsRamp.
January 1 - March 30: No templates were assigned, no consoles launched, no jobs or scripts were assigned. The device is considered active during this period.
March 31: The device is considered inactive.
April 1 - June 30: No templates were assigned, no consoles launched, no jobs or scripts were assigned. The device is continued to be considered inactive.
July 1: The device is removed from OpsRamp because it is inactive for 90 days, according to the data retention policy.

January 1: A device is onboarded in OpsRamp.
January 1 - March 30: No templates were assigned, no consoles launched, no jobs or scripts were assigned. The device is considered active during this period.
March 31: The device is considered inactive.
April 1: A template is assigned, or a console was launched, or a job or script was assigned. The device is considered to be active, according to the data retention policy.

January 1: A client is added in OpsRamp.
January 1 - March 30: No active device is being added to the client. The client is considered active during this period.
March 31 - The client is considered inactive.
April 1 - June 30: No active device is added to the client. The client is continued to be considered inactive.
July 1: The client is removed from OpsRamp because it is inactive for 90 days, according to the data retention policy.

January 1: A client is added in OpsRamp.
January 1 - March 30: No active device is being added to the client. The client is considered active during this period.
March 31: The client is considered inactive.
April 1: An active device is added to the client. The client is considered active, according to the data retention policy.

January 1: A partner is added in OpsRamp.
January 1 - March 30: No active client is being added to the partner. The partner is considered active during this period.
March 31: The partner is considered inactive.
April 1 - June 30: No active client is added to the partner. The partner is continued to be considered inactive.
July 1: The partner is removed from OpsRamp because it is inactive for 90 days, according to the data retention policy.

January 1: A partner is added in OpsRamp.
January 1 - Mar 30: No active client is being added to the partner. The partner is considered active during this period.
March 31: The partner is considered inactive.
April 1: An active client is added to the partner. The partner is considered active, according to the data retention policy.

January 1: A ticket is been created.
January 30: The ticket is closed.
January 31 – January 30 (the following year) – the ticket data is available in OpsRamp.
January 31 (the following year) – the ticket data is deleted from OpsRamp, according to the data retention policy.

January 1: A ticket is been created. The ticket data is available in OpsRamp as long as the ticket remains open, according to the data retention policy.

January 1: An alert is created.
January 30: The alert is suppressed or closed.
January 31 – April 30: The alert is available in OpsRamp.
May 1 – The alert is deleted from OpsRamp, according to the data retention policy.

January 1: An alert is created.
The alert data is available in OpsRamp as long as the alert is open, according to the data retention policy.

Example 1:

January 1: A report schedule is created and run, with the Now option.
April 1: This report schedule has not been re-run since it was first run on January 1.
This report schedule and the generated report are available until the last day of March and are deleted on April 1, according to the data retention policy.

Example 2:

January 1: A report schedule is created and run, with the Now option.
February 1: This report schedule was re-run to generate a newer version of the report.
This report schedule and the generated report are available until the last day of April and are deleted on May 1, according to the the data retention policy.

Example 3:

January 20: A report schedule is created with “Recurring” option, to be run monthly. Consequently, the report schedule is run on the first of every month, starting February 1.
This report schedule created by an “active” user is never deleted, according to the data retention policy.
Recurring reports generated from this schedule is removed, 90 days after they are generated, according to the data retention policy. For example: the report generated on February 1 is removed on May 1.

Example 4:

January 20: A report schedule is created with “Recurring” option, to be run monthly. Consequently, the report schedule is run on the first of every month, starting February 1.
February 20: The account of the user who created the recurring schedule is de-activated.
March 1: The monthly scheduled report will cease to run from March 1, as long as the user’s account is still de-activated.
March 20: The user’s account is re-activated.
April 1: The monthly scheduled report will resume from April 1.
April 20: The user’s account is de-activated again and continues to be de-activated for more than 90 days.
May 1: The monthly scheduled report will again cease to run starting May 1.
July 20: The user account will now be considered “inactive”.
July 1: The report schedule and generated reports are deleted, 90 days after its latest run on April 1, according to the data retention policy for reports.