ㅇㅌㅎㅅ4

이eun·2026년 3월 9일

좋은 포인트야 👍
지금 문서에는 Jobs / Scheduled jobs / History 탭 설명이 충분히 구조적으로 정리되어 있지 않아서 사용자 입장에서 “세 탭이 무엇이 다른지”가 명확하지 않아.

그래서 User Guide에서는 보통 Data Sync interface overview 섹션에서 세 탭을 먼저 설명해주는 게 좋다.
아래는 AWS 스타일로 정리해서 기존 문서 앞부분에 추가할 섹션이야.


Data Sync interface

The Data Sync page provides three tabs for managing and monitoring data synchronization jobs.

Each tab serves a different purpose in the data transfer lifecycle.

TabDescription
JobsDisplays all data sync jobs and allows users to manually run jobs.
Scheduled jobsDisplays jobs configured with schedules and allows users to manage scheduling settings.
HistoryDisplays execution records and results of completed or running jobs.

Jobs tab

The Jobs tab displays all configured data sync jobs in the workspace.

This page is primarily used to manage and trigger data sync jobs.

From this tab, users can:

  • View existing jobs
  • Manually run jobs
  • Monitor job execution status
  • Access job details

📷 Screenshot: Jobs tab

Displays all data sync jobs created in the workspace.


Scheduled jobs tab

The Scheduled jobs tab is used to manage scheduled data sync jobs.

This tab allows users to automate data transfers by defining execution schedules.

From this page, users can:

  • Create scheduled jobs
  • Monitor schedule status
  • Pause or resume schedules
  • Edit scheduling configurations
  • Duplicate schedules
  • Delete schedules

📷 Screenshot: Scheduled jobs tab

Displays scheduled data sync jobs and their scheduling status.


History tab

The History tab displays execution records of data sync jobs.

Users can use this page to review previous job executions and analyze transfer results.

This tab provides visibility into:

  • Job execution results
  • Transfer progress
  • Execution duration
  • Transfer throughput

📷 Screenshot: History tab

Displays historical execution records and performance metrics for data sync jobs.


Data Sync workflow

The three tabs represent the lifecycle of a data sync job.

Jobs
   ↓
Scheduled jobs (optional automation)
   ↓
History (execution results)
  • Jobs define what data to transfer
  • Scheduled jobs define when the transfer runs
  • History shows the result of the execution

이걸 문서 맨 앞쪽에 넣으면 사용자 이해도가 확 올라가.

실제 클라우드 문서들도 대부분 구조가 이렇게 돼:

Overview
↓
Interface (Jobs / Scheduled jobs / History)
↓
Creating jobs
↓
Scheduling
↓
Managing schedules
↓
Monitoring (History)

0개의 댓글