Tracers

Prev Next

Available in Classic and VPC

This section describes how to create or delete a tracer, change tracer settings, and view files exported to Object Storage in Tracers. To access the Tracers menu, access the NAVER Cloud Platform portal, click [Console], and navigate to i_menu > Services > Management & Governance > Cloud Activity Tracer > Tracers.

Tracers interface

The Tracers interface includes the following components:
cloudactivitytracer-use-tracers_screen_ko

Component Description
① Menu name Current menu name.
② Basic features Features displayed when you enter the Tracers menu for the first time.
  • [Create tracer]: Click to create a tracer (see Create tracer).
  • [Learn more]: Go to the Cloud Activity Tracer overview page.
  • [Refresh]: Reload the tracer list.
  • [Auto update (60s)]: If you click the button to enable it, the tracer list automatically refreshes every 60 seconds.
Change settings Click to change tracer settings (see Change tracer settings).
Delete Click to delete a tracer (see Delete tracer).
⑤ Tracer list List of created tracers (see View tracer list).
  • [View details]: This is enabled only when an item has more than 3 conditions set; click to view tracer detailed conditions.
  • [Rerun]: This is displayed when the export fails; click to run the export again.

View tracer list

To view created tracers in the tracer list:

Note

You can view the list only if there are 1 or more tracers created. If there are no tracers created, the list is not displayed on the Tracer interface.

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Management & Governance > Cloud Activity Tracer.
  2. Click Tracers.
  3. View the summary in the tracer list or click a tracer to check its details.
    cloudactivitytracer-use-tracers_list_ko
    • Tracer name: Name set when the tracer was created.
    • Tracer type: Type of the tracer.
      • DEFAULT: A type where a tracer name and detailed conditions cannot be set arbitrarily.
      • CUSTOM: A type where a tracer name and detailed conditions can be set arbitrarily.
    • Target Bucket (Region): Name of Object Storage's bucket to export and the bucket's Region information.
    • Final run results: Results of the export that was last conducted.
      • Initial: The status after creating a tracer but before exporting it to Object Storage.
      • Executing: The status when being exported to Object Storage.
      • Success: The status when the export to Object Storage is completed.
      • Fail: The status when the export to Object Storage failed.
    • Last run date: Date and time when the last export was conducted.
    • Tracer detailed conditions: Information about Region, Product, Account, and Tag set when the tracer was created.
    • Final cause of failure: The cause of the failure to export to Object Storage.
    • Date and time of change: Date and time when the tracer settings were last changed.
    • Creation date and time: Date and time when the tracer was created.
    • Tag: Assign tag keys/values to easily classify tracers.
      • View, create, edit, and delete all tags through [Tag management].
      • Only 1 tag value can be assigned to 1 tag key.

Create tracer

You can create a tracer and export the resource task history that meets the conditions set to Object Storage.
To create a tracer:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Management & Governance > Cloud Activity Tracer.
  2. Click Tracers.
  3. Click [Create tracer].
  4. In the Tracer creation popup window, enter the tracer information and click [Create].
    • You can select either Default or Custom as Tracer type.
      • You can create only 1 Default per account, and you cannot set the name and detailed conditions of the tracer arbitrarily.
    Caution

    Regardless of the type of tracer created, Object Storage is charged separately.

    • If you select Custom, enter the Tracer name and set Event conditions for the target tracer.
      • A name that duplicates another tracer is not allowed.
      • From the All resources list collected in Cloud Activity Tracer, you can export only the resources that meet the selected conditions to Object Storage.
      • For Region, Product, and Account, each of them is filtered with the AND condition. Multiple selections within Region, Product, and Account are filtered with the OR condition to perform the export.
      • The total number of events set to be exported is charged separately.
    • Select Target Bucket.
      • Region: List of Regions of the target Object Storage to export.
      • Bucket name: List of buckets of the target Object Storage to export.
      • If there are no buckets created, the [Create bucket] button is displayed. Click the button to create a bucket (see Create bucket).
    • You can select either JSON or CSV as a data transfer format.
      • If you select CSV, you can't export a data field if it contains data that exceeds the cell expression range (32767). In such a case, select JSON as the data transfer format.
    • Check the Object Storage transfer time and click the checkbox to select it.
      • For your activity history corresponding to the tracer condition, the data from a day ago is transferred to the bucket on a daily basis. 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.
      • Example: When a tracer is created on 2021-10-27
        * 2021-10-27 (upon creation): The data from 2021-07-29 00:00-2021-10-27 00:00 is transferred to Object Storage.
        => pub-tracer-test-daily-001-GMT+9-2021072900-2021102700-0.json
        * 2021-10-28 00:xx (GMT+9): The data from 2021-10-27 00:00-2021-10-28 00:00 is transferred to Object Storage.
        => pub-tracer-test-daily-001-GMT+9-2021102700-2021102800-0.json
        * 2021-10-29 00:xx (GMT+9): The data from 2021-10-28 00:00-2021-10-29 00:00 is transferred to Object Storage.
        => pub-tracer-test-daily-001-GMT+9-2021102800-2021102900-0.json
        - ...
        
    • In the tag component, enter the tag Key:Value to classify tracers.
Note

If export can't be performed due to the bucket deleted, changed permission, etc., from Object Storage, and the final run result is processed as failed, the [Rerun] button is displayed in Final run results. You can normalize the status, and then click the [Rerun] to perform the failed export task again.

Change tracer settings

To change the tracer settings:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Management & Governance > Cloud Activity Tracer.
  2. Click Tracers.
  3. Select a tracer you want to change the settings of and click [Change settings].
  4. In the Change tracer settings popup window, apply the items to change and click [Edit].
    • The [Edit] button is enabled only when there are changes.
    • You cannot change Tracer type.
    • For more information about each setting item, see Create tracer.
Note

The changed settings apply from the point of performing the next export.

Delete tracer

To delete a tracer:

  1. From the NAVER Cloud Platform console, navigate to i_menu > Services > Management & Governance > Cloud Activity Tracer.
  2. Click Tracers.
  3. Select the tracer you want to delete and click [Delete].
  4. Check the details in the Delete tracer popup window and click [Delete].
Note

Even when the tracer is deleted, data files exported to Object Storage are not deleted.

View Object Storage files

To view data files exported to Object Storage:

  1. From the NAVER Cloud Platform console, select the Region where the exported target bucket belongs.
  2. Navigate to i_menu > Services > Storage > Object Storage > Bucket Management.
  3. Click the target bucket you exported.
  4. Click the cat-tracer folder.
    • You can view the data file you exported.
    • To view details, click the file you want to view.
    • If you want to download a file, select the file to download and click [Download]. A JSON or CSV file is downloaded depending on the tracer settings.

Detailed description of the download file field

The detailed descriptions of the fields of the files downloaded from Object Storage are as follows:

Field name Description Examples
action Name of the resource change task createServerInstance
actionResultType Whether the resource change task succeeded SUCCESS/FAIL
actionSubAccountNo Number of the sub account that triggered the resource change task (same value as the SubAccountNo field of the View sub account list APIs) 10000
actionUserType Requesting user type
  • Customer: Main account
  • Sub: Sub account
  • 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 corresponding resource nrn:PUB:Server:KR:14---33:Server/1---4
    productData Details of the resources {"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
    Note
    • The field is identical for both CSV and JSON files.
    • The field order may change for CSV files, so it is recommended to use a JSON file when you convert it to a program.