> For the complete documentation index, see [llms.txt](https://docs.greennode.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greennode.ai/vstorage/datasync/giam-sat-dich-vu/giam-sat-datasync-thong-qua-log.md).

# 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](https://docs.greennode.ai/vmonitor.md).

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

<table data-header-hidden><thead><tr><th width="102"></th><th width="212"></th><th></th></tr></thead><tbody><tr><td>No.</td><td>Field</td><td>Meaning</td></tr><tr><td>1</td><td>@timestamp</td><td>Event start time (same as the <code>time</code> field).</td></tr><tr><td>2</td><td>rootUserAccountID</td><td>Account ID of the DataSync account.</td></tr><tr><td>3</td><td>size</td><td>Size of the transferred file, in bytes.</td></tr><tr><td>4</td><td>object</td><td>Name of the transferred file.</td></tr><tr><td>5</td><td>sourceObject</td><td>-</td></tr><tr><td>6</td><td>bucket</td><td>Source bucket name.</td></tr><tr><td>7</td><td>region</td><td>Source region.</td></tr><tr><td>8</td><td>endpoint</td><td>Source endpoint.</td></tr><tr><td>9</td><td>labels</td><td>-</td></tr><tr><td>10</td><td>taskid</td><td>Task ID: generated each time a Transfer Job runs.</td></tr><tr><td>11</td><td>jobid</td><td>Transfer Job ID: the transfer job id you create from the DataSync Portal.</td></tr><tr><td>12</td><td>statusCode</td><td>Status code indicating whether the transfer succeeded or failed.</td></tr><tr><td>13</td><td>source</td><td>Default: "datasync/access_log".</td></tr><tr><td>14</td><td>level</td><td>Default: "info".</td></tr><tr><td>15</td><td>host</td><td>Default: "VNGCLOUD".</td></tr><tr><td>16</td><td>time</td><td>-<br></td></tr><tr><td>17</td><td>objectType</td><td>Default: "*s3.Object".</td></tr><tr><td>18</td><td>destinationObject</td><td>-</td></tr><tr><td>19</td><td>bucket</td><td>Name of the destination container receiving data on vStorage.</td></tr><tr><td>20</td><td>region</td><td>Destination region receiving data.</td></tr></tbody></table>