Jobs
The Jobs module is a central hub for managing and monitoring tasks within OvalEdge. It provides a comprehensive view of all jobs, from initiation to completion, and offers tools for troubleshooting and analysis.
Key Features:
Job Main Page: View all running and completed jobs with their statuses (Initiated, Pending, Finished, Error).
Job Details: Access detailed information for each job, including:
ID, Name, and Type
Status breakdown (Initiated, Pending, Finished, Error) with descriptions for each state
Step details for multi-step jobs (ID, Name, Status) with explanations for each step status (Running, Waiting, Success, Partial Success, Error, Initiated, Killed)
Instance details (Server, VM)
The author who initiated the job
Start and End times, Duration, and processed data size.
Real-time Updates: Refresh the Jobs page to see the latest status and progress of running jobs. Automatic refresh can be enabled at set intervals.
Job Management: (for Authors)
Take actions on specific jobs: Kill (terminate), Initialize/Resume (start new or resume paused), Hold (pause)
Job Log Management: (for Authors)
View detailed logs for each job, including timestamps, status, commands, failures, and error messages.
Filter logs by date, search by keywords, filter by severity level (INFO, WARNING, ERROR), refresh for real-time updates, and download logs as CSV files for further analysis.
Job Permissions in OvalEdge
Authors with appropriate permissions can view all Jobs and their details.
Viewers cannot access any Jobs.
Admin-level Jobs are only visible to authors with the "OvalEdge Jobs Role."
Job System Settings: (for Administrators)
Configure job behavior and display:
Set role permissions for viewing job logs.
Define the maximum number of concurrent jobs.
Turn on/off the "Active Users & Jobs" tab in Application Diagnostics.
Set the interval for automatic page refresh.
Jobs in Detail
The Jobs page displays all running and completed jobs, along with their statuses and logs. Default Administrator (OE_Admin by default), along with Authors with appropriate role-based permissions, can view job details and perform necessary actions for each job.
The Jobs Grid View has the following columns:
Job ID: Each job has a unique ID and a descriptive name. Clicking the ID visually represents the job workflow (if applicable).
Job Name: Title of the job.
Job Status: Current status (Initiated, Pending, Finished, Error).
INITIATED: The job has commenced execution.
PENDING: The job has been created but has yet to start execution. It will remain pending until it's ready to be run.
FINISHED: The job is completed.
ERROR: The job encountered a failure.
Job Step ID: ID for the running activity (single-step or multi-step).
Single-step jobs execute as a whole.
Multi-step jobs have stages with IDs and names (some may link to details about related objects).
Job Step Name: Name corresponding to the step ID.
Job Step Status: Status of the step
RUNNING: Jobs are processed in the order they were submitted.
WAITING: A submitted job is queued and awaiting execution.
SUCCESS: The job has been completed successfully.
PARTIAL SUCCESS: The job was completed partially, but could not be finished.
ERROR: The job failed; authors can review error messages in the logs.
INIT: The job has been initiated.
KILLED: The task is terminated, halting job execution.
Type: This refers to the type of job (crawling, profiling, file table exchange).
Instance ID: It refers to the Server and VM details where OvalEdge runs.
Ext Job ID: This is the job ID from external platforms (Hadoop, Google Query) that matches the job step ID for internal jobs.
User: It refers to the name of the user who initiated the job.
Init Time: It refers to the date and time when the job was initiated.
Start Time: It refers to the date and time when the job began.
End Time: It refers to the date and time when the job is completed.
Duration: This refers to the total runtime of a job.
Size: It refers to the amount of data processed during the job execution.
Refresh Jobs
Authors can refresh the Jobs page for real-time updates on job status and progress during execution.
A toggle enables automatic refresh, with a default interval set to 30 seconds.
Page refresh timing can be configured in System Settings ("page.refresh.time").
Manage Jobs
Authors can manage jobs after initiation:
Select a job and click "Manage Jobs".
A menu offers options to:
Kill Job: Terminate and remove the job.
Initiate fresh job: The 'Initiate New Job' option allows authors to start or trigger an already executed job manually. A new job instance with a fresh ID will be created.
Run Now: The Run Now configuration defines the count of a separate queue for priority jobs, ensuring they can run even if they are stuck in the INIT state due to the ‘ovaledge.running.jobs.count’ limitation. For example, if the configuration limit is set to 3, then the maximum number of jobs that can be set to run now will be 3.
Run On Priority Queue: The ‘Run On Priority Queue’ helps to prioritize jobs in the INIT state. Users can set any number of jobs to run on the priority queue, but these will be prioritized only after the current execution jobs are done.
Jobs in the "Success" state cannot be killed.
Date Filter Jobs
Authors can filter jobs on the Jobs page by start and end dates. This lets them view all jobs executed within a specific date range.
Job Logs
Each job creates a log file detailing its actions. This file records events and processes within OvalEdge. Authors can view log details by clicking the eye icon.
Primary Logs
Primary logs refer to the standard or essential set of logs automatically captured by a system, application, or platform to record critical events and operational activity.
Viewing Job Log Details
The log window displays step-by-step information about the job execution.
It includes job creation, initiation, completion, and any actions by the scheduler (OvalEdge's job scheduling module).
Each run has multiple log entries for status and completion insights.
Details include timestamps, status, commands, failures, and error messages.
Managing Job Logs
Authors can use various features to analyze logs:
Date Filter: Filter logs by execution date.
Search: Find specific logs by keywords.
Log Value Filter: View logs based on severity (INFO, WARNING, ERROR).
Refresh Button: See real-time updates during job execution.
Download Button: Download logs as a CSV file for further analysis.
Page Metrics: The 'Page Metrics' provides a detailed overview of key performance indicators and diagnostic data for each job execution. The Page Metrics button is associated with every Job Log linked to a specific Job.
It captures critical metrics, such as Job Title, Job Duration, and Velocity (processing speed), along with counts of Application Database calls, Source System calls, and Asynchronous calls, which help in understanding system interaction and load. Additionally, it tracks SQL Error Counts, Log Error Counts, and Slow Queries Count, providing insight into potential issues that may impact performance or data quality. Each metric entry also includes a Page Request ID and the corresponding Page URL, allowing administrators to trace and troubleshoot specific requests within the application.
Extended Logs
Extended logs are additional, more detailed logs that capture comprehensive or specialized information beyond what is recorded in the primary logs.
Bridge Logs
Bridge Logs capture detailed execution information of data bridge jobs, including connection status, data extraction, and load activities. They help administrators monitor, troubleshoot, and validate data integration processes between OvalEdge and external systems.
Job Flow
The Job Flow provides a visual overview of job execution metrics, including workload, duration, processing velocity, and database call counts. It helps users analyze performance trends and identify bottlenecks across different stages of the job flow.
Jobs Summary
The Jobs Summary helps administrators quickly assess a particular instance's workload. It provides an overview of job status and distribution count, which helps identify trends in job execution.
The summary is divided into three sections: Current Open Jobs, Jobs Execution History, and Upcoming Jobs. The Current Open Jobs and Jobs Execution History provides essential details such as Instance ID, Last Run On, and the total number of jobs associated with different job statuses.
Upcoming Jobs are scheduled to run in the future, but have not yet started. These jobs may be in a queue or a scheduled list, and they are awaiting their designated start time or trigger event.
Job Alerts
The 'Job Alerts' allow authors to configure notifications for various system jobs. They can choose to receive alerts customized to their specific requirements.
Navigate to My Profile > System Alerts and here authors can configure alerts on different Jobs such as Crawling, Job Workflow (Notify on Success, Partial Success, or Failure), Connector Health Check, Missing Schema, Missing Domain, Malicious File, Download/Upload Data through Job, Download Lineage Data through Job, Down Stream Alert, Missing File Alert, AI Term Recommendation, Bridge Health Inactive/Active, License Verification, Rename Connection, Delegate Change, Connector Level Metadata Change, Compare Schema, and Jobs (Notify on Success/Failure).
Authors do find job-based alerts such as ‘Notify On Success’ and Notify On Partial Success’
Job Monitoring notifications are now triggered when a job becomes inactive because no logs are being generated. These alerts are delivered to the Inbox and via Email (if configured), ensuring timely awareness of inactive jobs. To prevent notification overload, repetitive alerts are suppressed. This enhancement helps reduce delays in corrective action and minimizes troubleshooting efforts.
Customization via System Settings
Administrators can configure job behavior and display it through System Settings:
ovaledge.jobs.view.role
Configure roles to view the job logs.
Parameters: Click on the field to select roles from the drop-down.
ovaledge.running.jobs.count
Specify the maximum number of concurrent (External or Internal) jobs that should run at a time.
External: Source system data processing jobs like crawl, profile, etc. Internal: Jobs that process the data within the application, like Applying Tags, Recommendations, etc.
Parameters: Allowed from 1 to 10. Enter the value in the field provided.
oe.diagnostics.activeusersandjobs.enable
Configure to enable the Active Users and Jobs tab on the Application Diagnostics page.
Parameters: If set to True, the Active Users and Jobs tab becomes accessible on the Application Diagnostics page. If set to False, the Active Users and Jobs tab is not available on the Application Diagnostics page.
page.refresh.time
Set the interval (in seconds) for automatic page refresh (default: 30 seconds).
Parameters: The default value is set to 30. Enter the value in the field provided.
ovaledge.skip.instances
It helps to skip jobs running on unwanted instances.
Parameters: The default value is Empty. Enter the instance name (generated in the database) in the field provided.
oe.object.search.count
To specify the number of records to appear on a single page for Jobs.
Parameters: The default setting is 20 records per page. Please input your desired value in the provided field.
ovaledge.enable.log4j
Configure to capture all the job execution logs in the application.
Parameters: The Default Value is set to False. If set to True, the metrics are captured. If set to False, the metrics are not captured.
buildlineage.exclude.jobtypes
Configure job types that need to be excluded from the Build Auto Lineage page. Parameters: Default value is Empty.
Enter the job types separated by a comma(,). Example: Single job type - View Multiple job types - View, Trigger
migration.jobs.trigger.mandatory
This setting is used to control the trigger of automatic migration jobs. Mark it as true if migration jobs need to trigger automatically, by default false.
inactive.job.threshold
Configure the time (in minutes) after which a job with no log generation is considered inactive.
Parameters:
Default value is 60 minutes. Enter the required threshold in minutes.
long.running.job.threshold
Configure the maximum duration (in hours) a job can run before it is considered long-running.
Parameters:
Default value is 24 hours. Enter the required duration in hours.
inactivejob.notification.timeout
Configure the time (in hours) to identify inactive jobs for notifications.
Parameters:
Default value is 24 hours. Enter the required timeout in hours.
jobs.priority.running.count
This configuration defines the count of a separate queue for priority jobs, ensuring they can run even if they are stuck in the INIT state due to the ovaledge.running.jobs.count limitation.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?