Tenable.io collector migration guide (1.x.x to 2.0.0)

1 Tenable Collector Migration Guide
- 1.1 Preparing for Migration
- 1.2 Migration Steps
  - 1.2.1 Step 1: Update Configuration

Tenable Collector Migration Guide

For users upgrading to version 2.0.0, changes in the configuration files need to be applied to ensure compatibility. This section provides step-by-step instructions for a smooth migration process and guidance on downgrading if needed.

Preparing for Migration

Backup Your Current Configuration: Ensure you have a backup of your existing configuration files before proceeding.
Review the New Configuration Changes: Familiarize yourself with the changes introduced in version 2.0.0, particularly regarding the config.yaml and config.json files.

Migration Steps

Step 1: Update Configuration

Changes in the config.yaml file:

The variable start_time has been renamed to start_date_utc. This change applies to the audit_log and plugins services.

Before (Version <2.0.0):

services:
  audit_log:
    request_period_in_seconds: <request_period_in_seconds_value>
    start_time: <start_time_value>
  plugins:
    request_period_in_seconds: <request_period_in_seconds_value>
    start_time: <start_time_value>

After (Version >=2.0.0):

services:
  audit_log:
    request_period_in_seconds: <request_period_in_seconds_value>
    start_date_utc: <start_date_utc_value>
  plugins:
    request_period_in_seconds: <request_period_in_seconds_value>
    start_date_utc: <start_date_utc_value>

Changes in the config.json file follow a similar pattern:

Before (Version <2.0.0):

{
  "services": {
    "audit_log": {
      "request_period_in_seconds": "<request_period_in_seconds_value>",
      "start_time": "<start_time_value>"
    },
    "plugins": {
      "request_period_in_seconds": "<request_period_in_seconds_value>",
      "start_time": "<start_time_value>"
    }
  }
}

After (Version >=2.0.0):