...
In the new version, to ingest the data we need to add that service name in the config.
user
is changed intousername
.credential
is changed intopassword
.username
andpassword
of the new version are undercredentials
subheading.There is no separate puller for any services all the services have a unified puller.
Preparing for Migration
Before starting the migration process, we recommend the following steps:
...
Code Block |
---|
# Old Version (1.x.x)
user: <user>
credential: <credentials>
|
↓
Code Block |
---|
# New Version (2.x.x)
services:
clicksBlocked:
start_time_in_utc_format: <start_time_in_utc_format> # example 2022-05-14T00:00:00Z
clicksPermitted:
start_time_in_utc_format: <start_time_in_utc_format> # example 2022-05-14T00:00:00Z
messagesBlocked:
start_time_in_utc_format: <start_time_in_utc_format> # example 2022-05-14T00:00:00Z
messagesDelivered:
start_time_in_utc_format: <start_time_in_utc_format> # example 2022-05-14T00:00:00Z
|
There are some changes in the params we are providing for each services in old and new configurations.
...
Code Block |
---|
# Old Version (1.x.x)
user: <user>
credential: <credentials>
|
↓
Code Block |
---|
# New Version (2.x.x) inputs: proofpoint_tap: id: <short_unique_id> enabled: true credentials: username: <username_value> password: <password_value> services: clicksBlocked: start_time_in_utc_format: <start_time_in_utc_format> # example 2022-05-14T00:00:00Z <override_tag>: <override_tag> clicksPermitted: start_time_in_utc_format: <start_time_in_utc_format> # example 2022-05-14T00:00:00Z override_tag: <override_tag> messagesBlocked: start_time_in_utc_format: <start_time_in_utc_format> # example 2022-05-14T00:00:00Z override_tag: <override_tag> messagesDelivered: start_time_in_utc_format: <start_time_in_utc_format> # example 2022-05-14T00:00:00Z override_tag: <override_tag> |
...
user
is changed intousername
credential
is changed intopassword
username
andpassword
in the new version must be put undercredentials
subheading.Number of requests all the services can make is 1800 in a day after that new calls will be blocked for a day.
By default
request_period_in_seconds
is 240 second so if norequest_period_in_seconds
param is provided in the user_config each service will starting new pull cycle after waiting for 240 seconds.