Vantage
License: PRO+ (Professional Edition or higher)
Plugin Type: File Action
Author: Diskover Data, Inc.
Overview
The Vantage file action integrates Diskover with Telestream Vantage, enabling users to submit media files directly to Vantage workflows for transcoding, proxy creation, and automated media processing. Instead of manually locating files and submitting them through Vantage's interface, users can select files in Diskover and send them to Vantage workflows with just a few clicks.
Telestream Vantage is an enterprise media processing platform widely used in broadcast, post-production, and media distribution environments. This integration bridges the gap between Diskover's powerful file discovery capabilities and Vantage's media processing workflows.
Key Features:
Direct workflow submission - Submit files to Vantage workflows without leaving the Diskover interface
Workflow organization - Browse workflows organized into logical groups (Language Services, QC, Editorial, etc.)
Real-time status tracking - Monitor job submission progress and view results
Job management - Access job history, view statistics, and resubmit failed jobs
Path translation - Automatic conversion between Diskover's indexed paths and Vantage-accessible paths
Multi-endpoint support - Route jobs to different Vantage servers based on geographic or organizational requirements
Use Cases
For Media Operations Teams:
Submit dailies or raw footage to proxy generation workflows directly from search results
Route media files to QC workflows for automated compliance checking before delivery
Send content to transcoding workflows for format conversion and distribution preparation
For Post-Production Workflows:
Submit source media to editorial preparation workflows
Route files to language services for captioning and audio description
Prepare content for streaming platforms with format-specific encoding
For Content Managers:
Quickly locate specific assets in Diskover and send them to processing without navigating multiple systems
Track job status and resubmit failed jobs from a centralized interface
Manage batch submissions for large content libraries
Requirements
Diskover Requirements
Requirement | Details |
|---|---|
Diskover Version | Compatible with current Diskover releases |
License | PRO+ (Professional Edition or higher) |
File Action Support | Must be enabled in your Diskover environment |
Vantage Requirements
Requirement | Details |
|---|---|
Telestream Vantage | Vantage Domain with REST API enabled (default port 8676) |
Network Access | Diskover workers must have network connectivity to the Vantage REST API |
Storage Access | Vantage server must have access to file paths (directly or via path translation) |
Storage Considerations
The Vantage server must be able to access files at the paths submitted through this file action. This typically means:
For on-premises storage: Vantage needs network share access to the same storage indexed by Diskover
Path translation rules may be required if Diskover indexes files using different mount points than Vantage uses
Installation
The Vantage file action is installed via RPM package on your Diskover environment.
Package Installation
dnf install diskover-file-actions-vantage
Service Restarts
After installation, restart the required services:
# On the Diskover Web host systemctl restart diskover-admin # On all Diskover Task Worker host(s) systemctl restart celery
Verify Installation
After restarting services:
Log into the Diskover web interface
Select one or more media files
Open the File Actions menu
Confirm "Vantage" appears as an available action
Configuration
Configuration is managed through the Diskover Admin interface at Diskover Admin → Configuration → Plugins → File Actions → Vantage.
Global Settings
These settings apply to all Vantage operations:
Setting | Default | Description |
|---|---|---|
workflow_age_limit_months | 6 | Only display workflows that have been modified within this many months. This helps hide stale or deprecated workflows from the selection interface. |
s3_region | us-west-1 | Default AWS region for S3 path translations (if using cloud storage) |
s3_timeout | 300 | Timeout in seconds for cloud storage operations |
job_priority | 0 | Default job priority (0-10, where 0 is lowest priority) |
include_username_in_jobname | true | When enabled, appends the submitting user's name to job names for easier tracking |
debug_mode | true | Enable detailed logging and response data for troubleshooting |
request_timeout | 10 | HTTP request timeout in seconds for Vantage API calls |
Vantage Host Configuration
The vantage_hosts section defines connection details for your Vantage server(s). Most deployments use a single Vantage endpoint.
Setting | Required | Description |
|---|---|---|
name | Yes | A friendly display name for this Vantage instance (e.g., "Production Vantage") |
host | Yes | The Vantage REST API URL including port (e.g., http://vantage-server:8676) |
rest_path | No | REST API path, defaults to /Rest |
workers | Yes | List of Diskover worker names that should use this endpoint |
enabled | No | Enable or disable this endpoint (default: true) |
Workflow Display Settings
Control how workflows appear in the selection interface:
Setting | Default | Description |
|---|---|---|
use_workflow_groups | true | Organize workflows into collapsible groups for easier navigation |
workflow_groups | (see below) | Define workflow categories and which workflows belong to each |
show_ungrouped_workflows | true | Display workflows that aren't assigned to any group |
ungrouped_section_name | "Other Workflows" | Label for the ungrouped workflows section |
default_workflow | (empty) | Pre-select this workflow ID when the interface loads |
active_workflows | (empty) | If specified, only show these workflow IDs (whitelist mode) |
Workflow Groups
Workflow groups organize your Vantage workflows into logical categories, making it easier for users to find the right workflow. Each group contains:
group: Display name shown in the interface
default: The workflow ID to pre-select when expanding this group
workflows: List of workflow IDs that belong to this group
Example workflow groups commonly used in media environments:
Group | Typical Use |
|---|---|
Language Services | Captioning, subtitling, and translation workflows |
QC | Quality control and compliance checking |
Editorial | Proxy generation and editorial preparation |
Audio | Audio extraction and processing |
Digital Services | Format conversion and distribution preparation |
Path Translation
Path translation converts the file paths indexed by Diskover into paths that the Vantage server can access. This is essential when Diskover and Vantage use different mount points or network paths to access the same storage.
Each path translation rule includes:
Setting | Description |
|---|---|
storage_type | Type of storage: fs (filesystem), s3, wasabi, gcp, or azure |
enabled | Enable or disable this translation rule |
from_path | The path prefix as it appears in Diskover's index |
to_path | The corresponding path as Vantage should access it |
Filesystem Path Translation Example
If Diskover indexes files at /mnt/media/ but Vantage accesses the same storage as \\fileserver\media\:
storage_type: fs from_path: /mnt/media/ to_path: //fileserver/media/
When a user submits /mnt/media/projects/video.mxf, it's translated to \\fileserver\media\projects\video.mxf for Vantage.
Note: Forward slashes are automatically converted to backslashes for Windows UNC paths.
Configuration Example: Single Vantage Server
This example shows a typical single-server deployment:
vantage_hosts:
- name: "Production Vantage"
host: "http://vantage.example.com:8676"
rest_path: "/Rest"
workers:
- "worker01"
- "worker02"
enabled: true
use_workflow_groups: true
workflow_groups:
- group: "Proxy Generation"
default: "workflow-uuid-1"
workflows:
- "workflow-uuid-1"
- "workflow-uuid-2"
- group: "QC"
default: "workflow-uuid-3"
workflows:
- "workflow-uuid-3"
show_ungrouped_workflows: true
ungrouped_section_name: "Other Workflows"
replacepaths:
- storage_type: "fs"
enabled: true
from_path: "/mnt/production/"
to_path: "//fileserver/production/"
- storage_type: "fs"
enabled: true
from_path: "/mnt/archive/"
to_path: "//fileserver/archive/"
Multi-Endpoint Deployments
For organizations with multiple Vantage servers (for example, in different geographic locations), you can configure multiple endpoints. Each endpoint is assigned to specific Diskover workers, allowing jobs to be routed to the appropriate Vantage server based on which worker handles the request.
This is configured by adding multiple entries to the vantage_hosts list, each with its own workers assignment and path translations.
Usage Guide
Submitting Files to Vantage
Step 1: Select Files
In the Diskover web interface, locate and select the media files you want to process. You can select multiple files using checkboxes.
Note: The Vantage file action only processes files, not directories. If you select directories, they will be filtered out.
Step 2: Launch the File Action
With files selected, access the File Actions menu and choose Vantage.
Step 3: Select a Workflow
The workflow selection interface displays available Vantage workflows organized into groups (if configured). Click a group header to expand it and see the workflows within.
Grouped workflows appear in collapsible accordion sections
Ungrouped workflows appear in the "Other Workflows" section
A radio button indicates the currently selected workflow
Select the workflow you want to use for processing your files.
Step 4: Submit the Job
Click Submit to send the selected files to the chosen Vantage workflow. Each file is submitted as a separate job.
Step 5: Monitor Progress
After submission, the status page displays real-time progress for each file:
Status | Meaning |
|---|---|
Pending | Job is queued and waiting to be processed |
Success | Job was successfully submitted to Vantage |
Failed | Submission encountered an error (check details for more information) |
Viewing Job History
Access the Jobs page through the Vantage file action menu to view submission history and statistics.
The Jobs page displays:
Summary statistics: Total jobs, queued, processing, complete, and failed counts
Job list: Filterable list of submitted jobs with status and details
Resubmit option: Failed jobs can be resubmitted directly from this interface
Tips for Efficient Workflows
Use search filters first: Narrow down your file selection in Diskover before launching the file action to avoid submitting unnecessary files
Check workflow age: If you don't see an expected workflow, it may have exceeded the workflow_age_limit_months setting—ask your administrator to adjust this if needed
Monitor job status: Keep the status page open after large batch submissions to catch any failures early
Use job names: When include_username_in_jobname is enabled, your submissions are easily identifiable in Vantage's job queue
Troubleshooting
Common Issues
Issue | Cause | Resolution |
|---|---|---|
"Failed to connect to Vantage API" error | Network connectivity or Vantage service issue | Verify the Vantage server is running and accessible from Diskover workers. Check that the configured host URL and port are correct. |
Jobs fail with "file not found" in Vantage | Path translation mismatch | Enable debug mode to see the translated path. Verify the from_path matches the Diskover index path exactly and to_path is accessible from the Vantage server. |
Expected workflow not appearing | Workflow age exceeds limit or not in active list | Check if the workflow was modified within workflow_age_limit_months. If using active_workflows, ensure the workflow ID is included. |
HTTP 200 but job shows all-zero identifier | Invalid workflow ID or inaccessible file path | Verify the workflow ID is correct and the translated file path is accessible to Vantage. |
Tasks remain in PENDING state | Celery worker not processing the queue | Verify the Celery worker is running and listening to the fileactions worker_name queue. Restart the celery service if needed. |
"Worker not set in session" error | Session timeout or configuration issue | Re-authenticate to Diskover to refresh your session. The file action defaults to "worker01" if no worker is found. |
Debug Logging
Enable detailed logging for troubleshooting by setting debug_mode: true in the configuration. This includes additional information in API responses and more detailed log entries.
Log Locations:
Component | Log File |
|---|---|
Diskover Admin | /var/log/diskover/diskover-admin.log |
Celery Workers | /var/log/celery/worker.log |
Web Server | /var/log/nginx/error.log |
Filtering Logs for Vantage:
# View Vantage-related entries in admin logs grep vantage /var/log/diskover/diskover-admin.log # View Vantage task activity in Celery logs grep vantage /var/log/celery/worker.log
Verifying Path Translation
If jobs are failing due to path issues:
Enable debug_mode in the configuration
Submit a test file and note the submission details
Check the original_path, translated_path, and vantage_path values in the response
Verify the vantage_path is accessible from the Vantage server
Support
Diskover Documentation: https://docs.diskoverdata.com
Diskover Support Portal: https://support.diskoverdata.com
Telestream Vantage Support: https://www.telestream.net/telestream-support/vantage/support.htm
Last Updated: January 2026
Diskover Data, Inc.
Comments
0 comments
Please sign in to leave a comment.