Simple Mode: Model Generation Setup

Table of Contents

• General Description
• 1. Selecting Assets for Connections
• 2. Model Metrics Configuration
• 3. Removing Circular Dependencies
• 4. Model Run Schedule

---

General Description

The simplified mode of model generation setup provides quick configuration through a visual designer without delving into technical details. Suitable for users who need to set up a model with minimal effort using standard templates.

---

1. Selecting Assets for Connections

Purpose of this step - to select data sources (assets) and arrange them in a sequence that will determine how data will be loaded and interconnected.

Asset Selection Interface

The screen displays a visual area with existing assets. Assets are sequentially selected in this area, forming a hierarchical structure.

Asset Sequence

The sequence can be configured in two ways: manually (step-by-step construction) or automatically (system path calculation).

Manual Construction (Step-by-Step)

Action	Result
1. Click on the first asset	Becomes the root node of the tree
2. Click on the second asset	Becomes a child of the first
3. Click on subsequent assets	Each new asset is linked to the previous one
4. Confirm the sequence by clicking the checkmark	The sequence will be added to the Model Generation Setup panel

Information

The order of addition determines nesting: parent - child element. It is possible to form multiple independent trees.

Automatic Path Calculation (From Start to End)

This method is suitable when the initial and final assets are known, and the system should determine all intermediate steps on its own.

Action	Result
1. Click on the initial asset	Becomes the root node of the tree
2. Click on the final asset	Asset is marked as the endpoint
3. System automatically finds all possible paths from start to finish	Route building taking into account connections between assets
4. Confirm the sequence by clicking the checkmark	The sequence will be added to the Model Generation Setup panel. Intermediate assets are automatically hidden

Editing the Sequence

After confirming the selection, the Model Generation Setup panel will open, where you can manage the sequence.

Action	Description
Delete Node	Remove unnecessary nodes from the sequence
Delete Sequence	Remove the entire sequence from the panel
Hide Node	Node is not displayed in visualization, but participates in data calculation for child nodes

Health Model

The Health Model panel - located parallel to the asset selection area.

After setting up and confirming the asset sequence in this area, the health model is automatically displayed. This allows you to visually verify the correctness of the constructed sequence before proceeding to the next step.

---

2. Model Metrics Configuration

Purpose of this step - to define the metrics template: what indicators will be collected for services, where to get them from, and how to aggregate them. The template is applied to all services automatically. For each service, the system will substitute its own values (via {{ ... }}) and generate metrics according to the specified rules.

Description

Metrics are indicators that characterize the state of a service (for example, CPU load, number of requests, response time).

At this step, global metrics (from the Service Monitor Toolkit monitoring system) are bound to services, and the method of their calculation is configured.

Service Structure

At the top, the Service Structure block is displayed - this is a list of previously configured services for which metrics will be collected.

Parameter Configuration

Parameter	What it defines	Example
Global Metric	Global metric available for binding	cpu_usage, request_duration
Metric Service Name	Template of the metric name for a specific service	{{ service.name }}_cpu
Description	Explanation of what the metric shows and how it is calculated	CPU load in percent
Filter Groups	Filtering metric objects by global dimensions (selecting indicators from the common pool)	namespace = {{ service.namespace }}
Common State Detection Function	Method of combining indicators into one service metric	avg, min, max

Step-by-Step Instructions

To create a new metric:

1. Click + Add Metric Structure
2. Select Service Monitor Toolkit Metric from the dropdown list
3. Enter a template using {{ ... }} in the Service Metric Name field
4. Fill in Description (recommended)
5. Add filtering conditions in the Filter Groups block
6. Select Aggregation Function (avg, min or max)

To edit a metric:

1. Click on the metric block
2. Change the required parameters
3. Changes are saved automatically

To delete a metric:

• click on the trash icon in the metric block

Filter Operation Principle

A global metric can contain data for multiple objects. Filters allow selecting only the data that relates to a specific service.

Example: global metric cpu_usage has dimensions: service_name, pod, namespace.

To bind it to service payment:

Parameter	Value
Service Monitor Toolkit Metric	cpu_usage
Filter Groups	service_name = "payment"
Service Metric Name	{{ service.name }}_cpu_usage

Information

Reference syntax: {{ node_name.field }}.

Aggregation Functions

When multiple metric values are found by filters (for example, multiple pods of a service), they need to be combined into one service metric.

Function	What it does	Example usage
avg	Arithmetic mean	Average CPU load across all pods
min	Minimum value	Lowest load (to identify idle pods)
max	Maximum value	Peak load (to identify overloaded pods)

---

3. Removing Circular Dependencies

Purpose of this step - to eliminate circular connections that may arise due to complex data structure and lead to incorrect model operation.

Step-by-Step Instructions

Automatic removal:

1. Click the Remove all cycles (n) button, where n is the number of found cycles
2. The system will automatically find and delete all circular dependencies

Manual removal:

1. Find the problematic connection in the interface (usually highlighted)
2. Click on the trash icon next to the dependency

---

4. Model Run Schedule

Purpose of this step - to configure the schedule according to which the model will be automatically recalculated.

Schedule Types

Type	Description	Example
Cron Expression	Flexible configuration through standard cron syntax	*/5 * * * * - every 5 minutes
Interval	Simple selection: start time/interval/units	01/01/2026 / 20 / days