For the complete documentation index, see llms.txt. This page is also available as Markdown.

Monitoring DataSync Through Logs

What is a log?

Logs are events collected at many different points in time. These events are usually generated by applications or services and contain full contextual information at the moment the event occurred.

Why are logs useful?

Logs are an important element of cybersecurity. When implemented correctly, logging gives us a clear view of what is happening or has happened in our system, allowing us to verify events with greater accuracy and make adjustments when needed.

Monitoring DataSync through DataSync logs on the vMonitor Platform

Monitoring DataSync through logs is easy with the vMonitor Platform, which is also a product in the GreenNode ecosystem. You can use it to configure monitoring features based on DataSync logs. To do so, you need to purchase the log quota package of the vMonitor Platform service; for details, refer to vMonitor Platform.

The log content pushed to the system includes the following fields:

No.

Field

Meaning

1

@timestamp

Event start time (same as the time field).

2

rootUserAccountID

Account ID of the DataSync account.

3

size

Size of the transferred file, in bytes.

4

object

Name of the transferred file.

5

sourceObject

-

6

bucket

Source bucket name.

7

region

Source region.

8

endpoint

Source endpoint.

9

labels

-

10

taskid

Task ID: generated each time a Transfer Job runs.

11

jobid

Transfer Job ID: the transfer job id you create from the DataSync Portal.

12

statusCode

Status code indicating whether the transfer succeeded or failed.

13

source

Default: "datasync/access_log".

14

level

Default: "info".

15

host

Default: "VNGCLOUD".

16

time

-

17

objectType

Default: "*s3.Object".

18

destinationObject

-

19

bucket

Name of the destination container receiving data on vStorage.

20

region

Destination region receiving data.

Last updated