Table: make_scenario_log
Scenario Logs allow you to explore past runs of your scenarios.
Key columns
- Provide a numeric
scenario_id
to query Scenario Logs for a specific Scenario. This can be either set directly in awhere
clause, or specified as part ofjoin
with another table. - Provide both a string
id
and a numericscenario_id
if you want to query for a specific Scenario Log.
Examples
List of all Scenario Logs
select *from make_scenario_logwhere scenario_id = 1;
List all non-auto scenario runs (errors, manual, etc.)
select *from make_scenario_logwhere scenario_id = 1 and type != 'auto';
Schema for make_scenario_log
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form, e.g. connection_name. | |
author_id | bigint | Author User ID. | |
duration | bigint | Duration of the run in milliseconds. | |
id | text | = | The Scenario Log ID. |
imt_id | text | The Internal execution ID. | |
instant | boolean | Instant run? | |
operations | bigint | Number of operations consumed. | |
organization_id | bigint | The Organization where the scenario belongs to. | |
scenario_id | bigint | = | Virtual column, used to map the entity to another object. |
status | bigint | Status of the run. | |
team_id | bigint | The Team where the scenario belongs to. | |
timestamp | timestamp with time zone | Date and time of the run. | |
title | text | The display name for the resource. | |
transfer | bigint | Transfer consumed in bytes. | |
type | text | Type of the run. |