Order Run Details¶

Find information and results on each order run in the UI or from the command line.

Access the Order Run Details page¶

Open a kitchen, then select ORDERS from the green menu. Click any Order Run ID to open the Order Run Details page.

Tour the Order Run Details page¶

The Order Run Details page displays a run status, testing and timing information, and logs for an entire order run and for each node in the graph.

The Order Run graph represents the variation's graph at runtime. It shows node processing statuses.

Under Order Run, the breadcrumbs provide quick access to return to the Recipes and Variation pages.
Order run toolbar:
- Conditions Results: opens a dialog with results from conditional node evaluations.
- Test Results: opens a dialog with results from all node tests.
- Timings Graph: opens a graph showing run times by node.
- Runtime Variables: opens a list of compiled variables (secrets display as vault paths).
- Logs: opens a dialog with log entries, filtering, and export functions.
- Run Variation Once: executes the graph again.
- Resume Order: begins executing a failed order at the point of failure.
- Variation Metrics over Time: opens the Variation Metrics page.
- Order Run Details: opens a drawer with general details about the order run.
A status message shows when order runs are planned, executed, failed, completed, or when they have stopped due to exceeding their set time limits.
Graph Mode selections change the appearance of the nodes. Choose from Node Status, Node Type, Node Components, and Number of Tests.
The Order Run graph represents the variation's graph at runtime. When you select Node Status as the Graph Mode, the graph shows the processing status
Select any node to open the Node Details with data specific to that node. Click Edit Node to access the Node Editor.
Select Show Legend for information on the node types, specific to the Graph Mode.
Click Export Graph to download a PNG or SVG file of the graph image.

Visual example in Automation¶

(Screenshot of the Order Run details page)

CLI order run details¶

You can access detailed information generated by any order run from the command line with the orderrun-info command.

Show order run summary

~$ dk orderrun-info --order_run_id 802213bc-3662-11e9-9f7b-0ad19868a29a --summary
Current context is: default
YYYY-MM-DD HH:MM:SS - Display Order-Run details from kitchen eric_dev

ORDER RUN SUMMARY

Order ID:       887d01ba-365e-11e9-8394-0242ac110002
Order Run ID:   802213bc-3662-11e9-9f7b-0ad19868a29a
Status:         COMPLETED_SERVING
Kitchen:        eric_dev
Recipe:         test_sources_sinks
Variation:      scheduled
Start time:     YYYY-MM-DD HH:MM:SS EST
Run duration:   0:00:12 (H:M:S)

Show order run timings

~ $ dk orderrun-info --order_run_id 802213bc-3662-11e9-9f7b-0ad19868a29a --timing
Current context is: default
YYYY-MM-DD HH:MM:SS - Display Order-Run details from kitchen eric_dev


TIMING RESULTS

  DKRecipe timing (test_sources_sinks), status = DKNodeStatus_completed_production
   total recipe execution time|0:00:12.205
   Node (redshift_source_test), status = DKNodeStatus_completed_production, timing is||0:00:02.345
    (redshift_source_test) Data Source(redshift_datasource) timing is||0:00:01.312
     (redshift_source_test) Notebook elapsed time is|None
   Node (s3_source_test), status = DKNodeStatus_completed_production, timing is||0:00:03.922
    (s3_source_test) Data Source(s3_datasource) timing is||0:00:02.891
     (s3_source_test) Notebook elapsed time is|None
   Node (node_with_downstream_test), status = DKNodeStatus_completed_production, timing is||0:00:01.439
    (node_with_downstream_test) Data Source(redshift_datasource) timing is||0:00:00.411
     (node_with_downstream_test) Notebook elapsed time is|None

Show order run tests

~ $ dk orderrun-info --order_run_id 802213bc-3662-11e9-9f7b-0ad19868a29a --test
Current context is: default
YYYY-MM-DD HH:MM:SS - Display Order-Run details from kitchen eric_dev

TEST RESULTS

Tests: Failed
        No Tests Failed

Tests: Warning
        No Tests Gave Warning Messages

Tests: Log
Step (node_with_downstream_test)
      1. log_time_minute_var_value (7 7)
Step (redshift_source_test)
      1. log_random_var_value (5 5)


Tests: Passed
Step (redshift_source_test)
      1. warning_if_random_var_value_is_identical_to_previous_run (5 not-equal-to 4 (previous-value of historic_calc_var)=4)
      2. warning_if_random_var_value_is_less_than_its_running_average (5 greater-than-equal-to 5 (running-average of historic_calc_avg_var)=5)
      3. warning_if_random_var_value_is_greater_than_5 (5 5 <= 5)
      4. warning_if_random_var_value_equals_3 (5 5 != 3)
      5. stop_on_error_if_static_query_result_does_not_equal_5 (5 query_result == 5)
Step (node_with_downstream_test)
      1. stop_on_error_if_downstream_test_of_count_files_pulled_does_not_equal_18 (18 count_files_pulled == 18)
Step (s3_source_test)
      1. stop_on_error_if_count_files_pulled_does_not_equal_18 (18 count_files_pulled == 18)

Note

If an order ID is not submitted as a parameter for the orderrun-info command details from the latest order run in the specified kitchen will be returned.