Manage scenarios
You can build scenario steps (workflows) using scenarios in Monitoring Flow. This guide explains how to manage scenarios in Monitoring Flow.
View scenario list
You can view the list of created scenarios and check basic information.
-
Go to KakaoCloud Console and select Monitoring Flow.
-
Check the list of created scenarios under the Monitoring Flow menu.
Item Description Scenario filter Filter or search for scenarios by keyword. Name Scenario name set by the user. Scenario ID Unique ID of the scenario. Flow connection Name of the flow connection. Schedule Execution schedule of the scenario.
- Uses a 5-part cron expression (e.g., "0 * 1 * *" → runs daily at 1 AM KST)
- Time-based (e.g., 30m → runs every 30 minutes)Last execution result Last execution status of the scenario.
-Succeeded
,Failed
- For details, see Scenario resultLast execution time Timestamp of the last execution
View scenario details
You can view the scenario's details and execution results.
-
Go to KakaoCloud Console and select Monitoring Flow.
-
Select the scenario you want to view.
-
Check detailed information from the scenario detail screen.
Item Description Scenario name Name set by the user. Scenario ID Unique ID of the scenario. Flow connection Flow connection linked to the scenario. Schedule Execution schedule.
- Uses a 5-part cron expression (e.g., "0 * 1 * *")
- Time-based (e.g., 30m)Last execution result Last execution status. See status reference Last execution time Timestamp of last execution
Scenario details by tab
- Details
- Execution result
You can view detailed settings including scenario name, ID, flow connection, schedule, last execution time, and result. You can also manage and edit scenario steps. The values shown reflect user-inputted original data and may vary per step.
Item | Description |
---|---|
Scenario step chart | Preview of the step structure. - Click each step to view its details on the right panel. |
Step name | Name given to the step. |
Step details | Settings configured for each step. |
API step details
Item | Description |
---|---|
Expected Code | Expected status codes for the API URL (up to 10). Defaults to 200 if not specified. |
Method | Selected API request method. |
URL | API URL. |
Parameters/Headers | Key/Value pairs set by the user. |
Body | Body content entered. |
Set Variables step details
Item | Description |
---|---|
Variable | Variable selected by the user. |
Step | Step name referenced. |
Key | Key value entered. |
For step details
Item | Description |
---|---|
Type | Type of For step (Count or ForEach). |
Count | Repetition count, if Count is selected. |
Base Variable | JSON List-type variable, if ForEach is selected. |
Marker Variable | Variable used to retrieve specific data. |
Marker Value | Value used to read data at specific positions. |
If step details
Item | Description |
---|---|
Logical | Logical function (and , or ). |
Left Operand | Left operand used in comparison. |
Comparison | Comparison operator (> , >= , < , <= , == , != ). |
Right Operand | Right operand used in comparison. |
Sleep step details
Item | Description |
---|---|
Sleep time | Time set for pause (up to 5 minutes). |
Check execution results and duration of completed scenarios. Results show substituted values based on user input and vary per step.
Item | Description |
---|---|
Date range filter | Filter execution logs by period (up to 1 month). |
Status filter | Filter by success or failure. |
View mode | Switch between chart or list view. |
Event | Timestamp of last execution (click to view step results). |
Status | Execution outcome. |
Execution time (sec) | Total execution time in seconds |
Execution type | Schedule |
Step execution result
Item | Description |
---|---|
Step | Step name (e.g., API-1). |
Execution time | Last execution time for the step. |
Execution result | Outcome of the step. |
Execution time (sec) | Time taken to execute. |
Event time filter | Filter to last 10 executions. |
Error details | Error logs if applicable. Check the panel on the bottom right. |
API step execution result
Item | Description |
---|---|
Response | Response from the API call. |
Status code | HTTP status code returned. |
Headers/Body | Output from headers/body. |
Method | API request method used. |
URL | API endpoint used (with variable values substituted). |
Request | Raw request input. |
Set Variables step execution result
Item | Description |
---|---|
Step | Referenced step name. |
Key | Key set by the user. |
Value | Retrieved value from the key. |
For step execution result
Item | Description |
---|---|
Type | Type of For step. |
Count | Repetition count if Count used. |
Base Variable | JSON List used in ForEach. |
Result table | Repetition count, marker values, and retrieved data. |
If step execution result
Item | Description |
---|---|
Logical | Selected logic (and , or ). |
Comparison operator | Expression entered. Substituted if variables used. |
Result | Evaluation result (True , False ). |
Sleep step execution result
Item | Description |
---|---|
Sleep time | Duration of sleep. |
Edit scenario
You can edit the name, flow connection, and schedule of an existing scenario.
- Go to KakaoCloud Console and select Monitoring Flow.
- Select the scenario to edit.
- Click the [Edit] button at the top of the Scenario list.
- After making changes, click [Save].
Copy scenario
You can copy an existing scenario. Scenario names must be unique.
- Only the scenario name can be changed during copy.
- Flow connection and schedule are inherited from the original.
- Go to KakaoCloud Console and select Monitoring Flow.
- Select the scenario to copy.
- Click the [Copy] button.
- Enter a new name and click [Copy].
Delete scenario
You can only delete scenarios that have no connected subnets.
Deleted scenarios cannot be recovered.
- Go to KakaoCloud Console and select Monitoring Flow.
- Select the scenario to delete.
- Click the [Delete] button.
- If any subnets are connected, disconnect them before deletion.
- Enter the scenario name to confirm, then click [Delete].
Use cases
Explore use cases of Monitoring Flow in Tutorials: