Bind Built-in Views¶

Bind user views to Explorers to enable correlated data analysis. When you view a specific data entry in the Explorer list, the side-sliding detail page will automatically display the matching built-in view, allowing for in-depth analysis without navigating away.

Getting Started¶

Step 1: Create a Binding¶

Navigate to Scenarios > Built-in Views > User Views > Bind.
Define a view name.
Define a custom identifier ID.
Select binding fields:
- Fixed fields: service (APM service), app_id (application), source (log source), project (project), label (label)
- Custom fields: Existing key and value pairs within the workspace.
Click Confirm.

Configuration Rules

At least one field must be added to establish the binding.
Supports wildcard matching for value.
Multiple fields have an "OR" relationship (matching any one field is sufficient).

Step 2: Verify the Binding¶

After configuring the binding, go to an Explorer where the data matches the bound field values.

Click on a target data row in the list. The corresponding built-in view will be displayed in the side-sliding detail page.

Step 3: Unbind¶

To remove a bound built-in view from the Explorer details, return to the Built-in Views page. Locate the view, clear the field content in its binding configuration, and click Confirm to unbind it.

Field Configuration Details¶

Value Matching Patterns¶

Pattern	Syntax Example	Matching Logic
Wildcard	`service:*`	All data containing the `service` field
Single Value	`service:value1`	Data where `service=value1`
Multiple Values	`service:value1,value2`	Data where `service=value1` OR `service=value2`
Fuzzy Match	`service:sql`	`service` values ending with `sql` (e.g., mysql, pymysql)

Multi-Field Priority¶

When multiple fields match different views simultaneously, the display priority is: service > app_id > source > project > label.

Example: * If service=value1, source=value2, project=value3 all match the same view, only that view is displayed in the detail page. * If they match different views, multiple views are displayed in order of priority (the service view appears first, followed by the project view).