Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Falcon has a wealth of information that can help users to triage issues relating to their pipelines, but this information is not available in a consumable form to the users. Here is a suggestion to solve for this issue to some extent.
In a typical usage scenario, users may find that their data has not been generated and that would require them to walk up the dependency tree to identify the root cause. Luckily all this information is available within Falcon and can be surfaced.
A mock of how this would look:
falcon instance -type feed -name FEED-abc -start 2014-10-01T00:00Z -end 2014-10-01T00:00Z -triage
FEED-abc/2014-10-01T00:00Z MISSING + PROCESS-def/2014-10-02T04:00Z WAITING + FEED-ghi/2014-10-01T00:00Z MISSING + PROCESS-mno/2014-10-01T01:30Z RUNNING + FEED-ghi/2014-10-01T01:00Z MISSING + PROCESS-mno/2014-10-01T02:30Z FAILED + FEED-ghi/* AVAIALBLE + FEED-jkl/* AVAILABLE
falcon instance -type feed -name FEED-abc -start 2014-09-01T00:00Z -end 2014-09-01T00:00Z -triage
FEED-abc/2014-09-01T00:00Z AVAILABLE
falcon instance -type process -name PROCESS-def -start 2014-10-01T00:00Z -end 2014-10-01T00:00Z -triage
PROCESS-def/2014-10-02T04:00Z WAITING + FEED-ghi/2014-10-01T00:00Z MISSING + PROCESS-mno/2014-10-01T01:30Z RUNNING + FEED-ghi/2014-10-01T01:00Z MISSING + PROCESS-mno/2014-10-01T02:30Z FAILED + FEED-ghi/* AVAIALBLE + FEED-jkl/* AVAILABLE
Attachments
Attachments
Issue Links
- is blocked by
-
FALCON-1039 Add instance dependency API in falcon
- Closed
- links to