Feature Request: Enhanced Observability and Traceability in IDP Workflows
O
Open Coral
Problem Statement
The current Workflows Execution History view lacks the necessary metadata and navigation links to efficiently troubleshoot failed tasks. Users cannot easily correlate a workflow execution (e.g., "Deploy Subscription") with its underlying CI/CD pipeline run, and the filtering capabilities are too limited for environments with high execution volumes.
Proposed Enhancements
- Direct Pipeline Linking (Traceability)
Request: Add a direct hyperlink to the specific Harness Pipeline Execution instance associated with each Task ID.
Value: Currently, when a workflow status is "failed," users must manually search for the corresponding pipeline in the CI/CD module. A direct link reduces the "Mean Time to Repair" (MTTR) by allowing one-click access to logs.
- Advanced Filtering & Search
Text-Based Search: Implement a global search bar that parses Task IDs and Template names.
Enhanced Column Filters: Add the ability to filter by:
Project/Organization: Narrow down tasks by specific business units.
Status: Quickly isolate "failed" vs. "completed" runs.
Date Range: Filter executions within specific time windows.
- Expanded Metadata Columns
Add a "Project" or "Target Environment" column to the main table. This provides immediate context without requiring the user to click into each Task ID.
User Experience Impact
By implementing these changes, Platform Engineers and Developers will spend less time "hunting" for data and more time resolving infrastructure issues. This transforms the Workflows view from a simple log into a functional diagnostic dashboard.
Log In