Monitoring

Available in VPC

This guide explains how to monitor batch jobs and apps submitted by Data Forest.

In the Monitoring menu, you can view the status and resource usage of batch jobs run in Data Forest and monitor apps created in Data Forest.

Batch job monitoring

To view batch job metrics:

1. In the VPC environment on the NAVER Cloud Platform console, navigate to Menu > All Services > Big Data & Analytics > Data Forest > Monitoring.

2. Click the [Batch] tab.

3. Select the account where you performed the batch job.

4. Check the batch status of the account.
   

   Item	Description
   Status	Status of batch jobs
   ID	Unique ID value of batch job performed
   Batch name	Name of batch jobs
   Queue	Information of queues requested by batch jobs
   Start time	Date and time when the batch job was started
   End time	Date and time when the batch job was ended
   Execution time	Time taken to run the batch job

Batch resource monitoring

You can view the indicators for resource usage used by batches (excluding app resources). When you select the account where the batch was performed, you can view the indicators for average memory usage during the past day, week, and month in a graph.

To view the indicators for batch resource usage, follow these steps:

1. In the VPC environment on the NAVER Cloud Platform console, navigate to Menu > All Services > Big Data & Analytics > Data Forest > Monitoring.
2. Click the [Batch-resources] tab.
3. Select the account where the batch was performed.
4. Check the memory usage.
   

App resource monitoring

To view the metrics for resource usage of the web you created:

1. In the VPC environment on the NAVER Cloud Platform console, navigate to Menu > All Services > Big Data & Analytics > Data Forest > Monitoring.
2. Click the [App] tab.
3. Select the account and app.
   
4. Check the application information.

   Item	Description
   App name	App name
   Queue	Information on the queue in which the app is running
   Status	App's status information
   Start time	Date and time when the app was started
   End time	Date and time when the app was ended
   Execution time	Time taken to run the app
   allocated memory(MB)	Amount of memory allocated to the app ( MB; -1 for completed apps)
   allocated cpu(vcpu)	Number of vCPUs allocated to the app (-1 for completed apps)
   memorySeconds(s)	Amount of time for which memory was allocated to the app (unit: second(s))
   vcoreSeconds(s)	Amount of time for which CPU was allocated to the app (unit: second(s))