- Print
- PDF
Tracers
- Print
- PDF
Available in Classic and VPC
This document explains how to create or delete tracers, modify settings of a tracer, and how to see the files exported to Object Storage. To access the Tracers menu, connect to the NAVER Cloud Platform portal, click the [Console] button, and then click the Services > Management & Governance > Cloud Activity Tracer > Tracers menus, in this order.
Tracers page
The Tracers page is laid out as follows.
Field | Description |
---|---|
① Menu name | Name of the menu currently being viewed |
② Basic features | Features provided on the first page when the user enters the Tracers menu |
③ Change settings | Click to modify the tracer settings. (Refer to Change tracer settings.) |
④ Delete | Click to delete the tracer. (Refer to Delete tracer.) |
⑤ Tracer list | The list of tracers created (Refer to View tracer list.) |
View tracer list
The following describes how to view a tracer created from the tracer list.
You can see the list only when there is one more tracers created. If there is no tracer created, then the list isn't shown in the Tracer page.
- From the NAVER Cloud Platform console, click the Services > Management & Governance > Cloud Activity Tracer menus, in that order.
- Click the Tracers menu.
- Check the summary information in the tracer list, or click a tracer to see the details.
- Tracer name: name of the tracer set upon creation
- Tracer type: type of the tracer
- DEFAULT: You can't set the name and detailed conditions for a tracer of this type.
- CUSTOM: You can set the name and detailed conditions for a tracer of this type.
- Target bucket (region): name and region information of the bucket in Object Storage for export
- Last run result: the result of the last export
- Initial: the status in which the tracer is created, but not yet exported to Object Storage
- Executing: the status in which an export to Object Storage is in progress
- Success: the status in which the export to Object Storage has been completed
- Fail: the status in which the export to Object Storage has failed
- Last run date and time: date and time of the last export
- Detailed tracer condition: information of the region, product, account, and tag set up upon creation of the tracer
- Cause of last failure: the cause of failure in exporting to Object Storage
- Modification date and time: date and time when tracer settings have been modified last
- Creation date and time: date and time when the tracer was created
Create tracer
You can create a tracer, and export resource activity history that fits the conditions set up to Object Storage.
The following describes how to create a tracer.
- From the NAVER Cloud Platform console, click the Services > Management & Governance > Cloud Activity Tracer menus, in that order.
- Click the Tracers menu.
- Click the [Create tracer] button.
- Enter the tracer information in the tracer creation pop-up window, and then click the [Create] button.
- You can choose the Tracer type between Default and Custom.
- One tracer of the Default type can be created per account. You can't set the tracer name and detailed conditions arbitrarily.
CautionFee for Object Storage is additionally charged, regardless of the created tracer type.
- If you chose Custom, enter the tracer name, and set up the tracer target event conditions.
- The tracer name must be unique.
- From All resources list collected by Cloud Activity Tracer, you can only export resources that fit the selected conditions to Object Storage.
- Region, product, and account are filtered by the AND condition. Multiple selections within the region, product, and account are filtered by the OR condition for export.
- An additional fee is charged for the total sum of events set up for export.
- Select the target bucket.
- Region: region list of the Object Storage which is the export target
- Bucket name: Bucket list of the Object Storage which is the export target
- The [Create bucket] button is displayed if there are no buckets created. You can click it to create a bucket. (Refer to Create bucket.)
- Transmission data format can be chosen between JSON and CSV.
- If you choose CSV, you can't export a data field if it contains data that exceeds the cell's expression range (32767). In such a case, select JSON as the transmission data format.
- Check when it's to be sent to Object Storage, and click the checkbox to select it.
- The user's activity history pertaining to the tracer condition is transferred to the bucket on a daily basis. The data sent is of the day before. However, the activity history from the last 90 days until the day before is exported in bulk to Object Storage, when creating a new tracer.
When a tracer is created on 10-27-2021 * 10-27-2021 (creation): The data from 07-29-2021 00:00 to 10-27-2021 00:00 is sent to Object Storage. => pub-tracer-test-daily-001-GMT+9-2021072900-2021102700-0.json * 10-28-2021 00:xx (GMT+9): The data from 10-27-2021 00:00 to 10-28-2021 00:00 is sent to Object Storage. => pub-tracer-test-daily-001-GMT+9-2021102700-2021102800-0.json * 10-29-2021 00:xx (GMT+9): The data from 10-28-2021 00:00 to 10-29-2021 00:00 is sent to Object Storage. => pub-tracer-test-daily-001-GMT+9-2021102800-2021102900-0.json - ...
- You can choose the Tracer type between Default and Custom.
If export can't be done due to bucket deleted, changed permission, etc., from Object Storage, and the final execution result is processed as failed, the [Rerun] button is displayed in Final execution result. The user can normalize the status, and then click the [Rerun] button to rerun the failed export task.
Change tracer settings
The following describes how to change tracer settings.
- From the NAVER Cloud Platform console, click the Services > Management & Governance > Cloud Activity Tracer menus, in that order.
- Click the Tracers menu.
- Select the tracer to change the settings, and then click the [Change settings] button.
- Apply the changes in the tracer settings modification pop-up window, and then click the [Change] button.
- The [Change] button will be enabled only when there are changes.
- You can't change the Tracer type.
- For more details about each item, refer to Create tracer.
The changed settings will apply from the point of running the next export.
Delete tracer
The following describes how to delete a tracer.
- From the NAVER Cloud Platform console, click the Services > Management & Governance > Cloud Activity Tracer menus, in that order.
- Click the Tracers menu.
- Select the tracer to delete, and then click the [Delete] button.
- Check the details in the tracer deletion pop-up window, and then click the [Delete] button.
Data files exported to Object Storage are not deleted, even when the tracer is deleted.
View Object Storage files
The following describes how to view data files exported to Object Storage.
- From the NAVER Cloud Platform console, select the region where the target bucket exported belongs.
- Click the Services > Storage > Object Storage > Bucket Management menus, in that order.
- Click the target bucket exported.
- Click the cat-tracer folder.
- You can view the exported data file.
- Click the file to view details to see the details.
- To download files, select the file to download and click the [Download] button. JSON or CSV files will be downloaded according to the Tracer settings.
Detailed description of the download file field
The detailed descriptions for the fields of the files downloaded from Object Storage are as follows.
Field name | Description | Example |
---|---|---|
action | Name of the resource change task | createServerInstance |
actionResultType | Success or failure of the resource change task | SUCCESS/FAIL |
actionSubAccountNo | Number of the sub account that triggered the resource change task (same value as the SubAccountNo field of the sub account list search API) | 10000 |
actionUserType | Requesting user type | Customer/Sub |
domainCode | Domain code (fixed value) | PUB |
eventTime | Time when the resource change task was created (epoch (Unix) time) | 1621584442893 |
historyId | Unique ID of the resource change task | 60a74edddcee96b0dcba0e60 |
nrn | Unique key value that can identify the resource | nrn:PUB:Server:KR:14---33:Server/1---4 |
productData | Details of the resource | {"hostName":"test-server","asyncTaskUuid":"ae339ad9-6f46-...-537369cb1444","...":"..."} |
productDataStatus | Resource status after the resource change task has been created | running |
productName | Service code of the resource | Server |
regionCode | Region code of the resource | KR |
regionName | Region name of the resource | Korea |
resourceType | Resource type of the resource | Server |
sourceIP | Client IP that triggered the resource change task | 1.1.1.1 |
sourceSubType | Detailed type of the request that triggered the resource change event | AUTO_SCALING/INTERNAL |
sourceType | Type of the request that triggered the resource change event | CONSOLE/API/SYSTEM/ADMIN |
- The field is identical for both CSV and JSON files.
- Since the field order may change for CSV files, it is recommended that you use a JSON file when you convert it to program.