Description Usage Arguments Value See Also Examples
Data is stored heavily within ScrapeBot. Hence, filtering needs to be applied to collect data. Two types of filter are possible:
Filter on the runs for which to collect data: Specify one or many of run_uid
, instance_uid
, and recipe_uid.
At least one is required.
Filter on the step for which to collect data: Optionally specify a step_uid
.
In general, this function only returns data from "success"-ful runs (see get_runs()
). It then collects runs matching the first set of criteria (i.e., run_uid
, instance_uid
, and recipe_uid
). Ultimately, it collects data, thereby focusing on a specific step if specified.
1 2 3 4 5 6 7 | get_run_data(
connection,
run_uid = NULL,
instance_uid = NULL,
recipe_uid = NULL,
step_uid = NULL
)
|
connection |
A connection object, as retrieved from |
run_uid |
Optional numeric UID or a vector of numeric UIDs of a specific run to collect data from. If |
instance_uid |
Optional numeric UID or a vector of numeric UIDs of the instance to filter data for. If |
recipe_uid |
Optional numeric UID or a vector of numeric UIDs of the recipe to filter data for. If |
step_uid |
Optional numeric UID or a vector of numeric UIDs of a step to filter data for. Defaults to |
A tibble listing all data including their creation timestamp, the UIDs of its run, instance, recipe, and step, as well as the data value itself.
1 2 3 4 5 6 7 8 9 10 11 12 13 | ## Not run:
connection <- connect('my_db on localhost')
get_run_data(connection, instance_uid = 42)
get_run_data(connection, run_uid = 256)
get_run_data(connection, recipe_uid = 21)
get_run_data(connection, run_uid = c(256, 1024))
get_run_data(connection, recipe_uid = 21:23)
get_run_data(connection, instance_uid = 42, recipe_uid = 21)
get_run_data(connection, instance_uid = 42, recipe_uid = 21, step_uid = 8)
disconnect(connection)
## End(Not run)
|
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.