View Categories

Glossary

4 min read

Acknowledge (Ack)
Mark an execution in error as “reviewed.” The status remains (e.g., ERROR) but is flagged as Acked to reduce noise. (See: Execution Status)

Admin (Role)
Full access to configure EAC: users/roles, jobs, tasks, servers, environments, purge policies, and settings. (See: API Role)

API (Role)
Programmatic access via tokens to trigger tasks and read execution data within scope; cannot alter global settings or users. (See: API Token)

API Token
Credential used by the API role to authenticate requests (e.g., start a task, query execution status). Keep tokens secret. (See: API Role)

APP_DEFAULT_URI
Base URL of the application used in links and callbacks. Configured in Settings (.env.local). (See: Settings vs .env)

APP_SERVER_NAME
Unique server name set in .env.local and mirrored in the Server definition in the UI. Used to match runtime hosts to configured servers.

APP_TASK_LOG_TYPE
Where task logs are stored: file or db. Affects visibility, retention, and purge mechanics. (See: ETL Logs)

Averaged Executions (EXEC_TASK_AVG_COUNT)
Number of recent runs used to compute average durations/progress estimates.

Context (Parameters)
Key–value pairs injected at runtime (e.g., database, dates, flags). Defined in Task Setup and/or Context Files. (See: Context File)

Context File
A versioned context configuration bundled with a JobVersion (can differ by environment). UI displays a matrix per context.

Cron / Schedule / Periodicity
Timing expression for scheduled tasks (supports seconds). Validated in UI; shown in human-readable form. (See: Scheduler)

Cron User (EAC_CRON_USER)
System user under which cron jobs are checked/executed (e.g., for eac:scheduler).

DATABASE_URL / DATABASE_URL_ETL_LOG
Connection strings for the core app DB and (optionally) a separate ETL logs DB. Credentials may require URL percent-encoding. (See: Percent-Encoding)

Deployment (JobVersion)
The process of making a packaged ETL job available to EAC servers. EAC never overwrites previous versions. (See: JobVersion)

Deployment Directory (APP_DEPLOY_DIR)
Local path on each server where job versions are stored.

Execution (Run)
A single run of a Task. Has an ID, timestamps, duration, type (Manual/Scheduled/API), server, job version, and status. (See: Task)

Execution ID
Unique identifier of a run; used to fetch logs/status and to stop/kill.

Execution Server (“Slave”)
A worker host that runs tasks. EAC schedules to a healthy server that has the correct job version locally. (See: Server Status, Rsync)

Execution Status
IN_PROGRESS, SUCCESS, WARNING, ERROR, KILLED, Acked, Not Acked. Drives colors and alerts across UI.

Follow the New Version (Task Setting)
When enabled, a task tracks the latest deployed JobVersion. When disabled, the task is pinned to a specific version. (See: Pinning)

Heartbeat / Server Status
Periodic metrics EAC collects from each execution server (CPU, memory, reachability, etc.). Used for scheduling decisions and UI health. (See: Server Status Purge)

History Purge Mode
Retention mode that keeps executions for the last X days. (See: Purge Policy)

Identifier (Execution Identifier)
Optional business key passed when starting a run (e.g., batch ID); appears in lists and helps correlation.

Job
A logical ETL artifact (e.g., Talend job) that can have multiple Tasks and multiple JobVersions. (See: Task, JobVersion)

JobVersion
A specific compiled/deployed version of a Job (e.g., 1.10.0, 0.1). Includes context files and optional screenshots of sub-tasks.

JVM Parameters (Xmx/Xms, …)
Java runtime flags stored per JobVersion and editable via commands/UI to control memory and tuning.

Kill (Execution)
Force-stop a running execution. Prefer Stop when available; kill is a last resort.

Log Types (ETL)

  • Talend Logs: application logs (ETL_LOG_TABLE_NAME)
  • Talend Stats: per-run stats (ETL_STAT_TABLE_NAME)
  • Talend Metrics: metrics (ETL_MET_TABLE_NAME)
    Configured via Settings; require proper indexing and retention. (See: ETL Logs)

MD5 (JobVersion Hash)
Checksum used to verify deployment consistency across servers during replication checks.

Percent-Encoding (URL)
Encode special chars in usernames/passwords inside URLs: @→%40, :→%3A, /→%2F, &→%26, %→%25, +→%2B, #→%23, ?→%3F. (Encode credentials only.)

Pinning (Task → JobVersion)
Explicitly selecting a JobVersion in Task Setup and unchecking Follow the new version to prevent automatic upgrades.

Project
Top-level grouping of Jobs/Tasks. Shown in breadcrumbs and list columns when multiple projects exist.

Purge (Task)
A task that deletes old executions/logs according to a Purge Policy. Can be scheduled and monitored like any task.

Purge Policy
Retention strategy for executions/status/log tables (e.g., history X days vs total fixed count). (See: Server Status Purge)

Reschedule Old Tasks After X Minutes
When the scheduler restarts, decides if (and how far back) missed schedules should be re-queued.

Rsync (Replication Service)
File sync mechanism used to distribute JobVersions to all execution servers. Checked by eac:check-jobversion-deployment. (See: Deployment Verification)

Scheduler
Internal process (CLI command) that launches scheduled tasks per their cron expressions; can be started/stopped from the UI.

Scope
Logical partition (e.g., environment/project/tenant) used for filtering, scheduling, and API calls.

Server Code (EAC_SERVER_CODE)
Identifier for the current instance/role (e.g., master). Displayed in UI and logs.

Server Status Purge
Scheduled task that deletes old per-minute server statuses (e.g., keep 4 days). Only the last minute is required for scheduling; older data is used only for historical views.

Settings vs .env
Settings page writes to .env.local (overrides). .env contains committed defaults. Real OS env vars have the highest precedence. Never commit secrets.

Shell Command Path (PHP_PATH_COMMAND)
CLI path for PHP used by EAC to run console commands.

Stop (Execution)
Graceful request to end a run. May escalate to Kill if the process doesn’t stop.

Task
Executable wrapper around a JobVersion with its schedule, contexts, and runtime options. A task can have many Executions over time.

Task Copy
Utility to duplicate a task’s configuration (contexts, schedule, options) as a starting point.

Task Setup
Configuration screen where you select the JobVersion, contexts, schedule, parallelism, mail options, etc.

Timeline (Executions Timeline)
Visualization of executions over time (default last 24h); supports hover tooltips, grouping by task, and filters.

Total Purge Mode
Retention mode that keeps only the last N executions, regardless of age.

Upload & Deploy
UI flow to upload an archive and deploy it as a new JobVersion (with automatic post-deploy checks).

User Roles

  • Admin — full configuration/control
  • API — automation: trigger/read only, scoped by token

Warning (Status)
Non-fatal condition during execution; does not trigger error emails when configured accordingly.