Skip to content

Bind Inner Views

Guance supports custom binding of inner views (user views) to explorers. By associating the inner view with Trace services, applications, log sources, projects, or other custom fields, explorers matching the field values can view the newly bound inner view through the sliding detail page.

Note: Explorers that support custom binding of inner views include scene-specific explorers, Infrastructure, Logs, Traces, Services, RUM, Security Check and Synthetic Tests.

Step Explanation

Go to Inner Views > User Views > Bind:

Create binding relationship

You can bind the inner view with the explorer based on trace service, app_id, log source, project, label or the key, value within the custom input space; fuzzy matching of value is supported.

Note: To ensure data consistency, when creating a binding relationship between user views and explorers, at least one field in the specified object category must be added as the binding relationship of this inner view, and the system will automatically synchronize the inner view based on this binding relationship.

View the bound inner view in the explorer details

After configuring the binding relationship, you can go to the explorer's sliding detail page that matches the bound field value to view the inner view.

Delete the bound inner view in the explorer details

If you need to delete the inner view that has been bound in the explorer details, clear the field content in the Bind and click Confirm.

Field Explanation

When binding fields in the inner view, in addition to the data range of the following fixed fields, it also supports generating binding relationships with the existing fields(key), field values(value) in the custom input space.

Field Data Range
Range
 Value Range
service The service value in the current workspace Tracing data
  • Scenes > Explorers
  • Infrastructure > All Explorers
  • Log Explorer
  • Traces
  • RUM > Session, View
  • Security Check Explorer
  • Synthetic Tests Explorer
    		•  *: Represents matching all services
    value: Represents only matching the corresponding service, supports single value matching, multi-value matching, fuzzy matching, etc.
    app_id The app_id value in the current workspace View data
  • Scenes > Explorers
  • Infrastructure > All Explorers
  • Log Explorer
  • Traces
  • RUM > Session, View
  • Security Check Explorer
  • Synthetic Tests Explorer
    		•  *: Represents matching all applications
    value: Represents only matching the corresponding application, supports single value matching, multi-value matching, fuzzy matching, etc.
    source The source value in the current workspace Logging data
  • Scenes > Explorers
  • Infrastructure > All Explorers
  • Log Explorer
  • Traces
  • Security Check Explorer
  • Synthetic Tests Explorer
    		•  *: Represents matching all log sources
    value: Represents only matching the corresponding log source, supports single value matching, multi-value matching, fuzzy matching, etc.
    project The project value in the current workspace's Object data
  • Scenes > Explorers
  • Infrastructure > All Explorers
  • Log Explorer
  • Traces
  • RUM > Session, View
  • Security Check Explorer
  • Synthetic Tests Explorer
    		•  *: Represents matching all projects
    value: Represents only matching the corresponding project, supports single value matching, multi-value matching, fuzzy matching, etc.
    label The label value in the current workspace's Object data Infrastructure > All Explorers *: Represents matching all projects
    value: Represents only matching the corresponding label, supports single value matching, multi-value matching, fuzzy matching, etc.
    Logic of binding field display in explorer details page:

    The value of the bound field supports 4 modes: *, single value, multiple values, and fuzzy matching.

    • If the value is set to *, such as service:*, the inner view will be bound to the details page of the explorer where the service field exists in any list;
    • If the value is set to a "single value", such as service:value1, the inner view will be bound to the details page of the explorer where service=value1 exists in any list;
    • If the value is set to "multiple values", such as service:value1,value2, the inner view will be bound to the details page of the explorer where service=value1 or service=value2 exists in the list data; if there are multiple key:value, such as service:value1 and source:value2, the inner view will be bound to the details page of the explorer where service=value1 or source=value2 exists in any list;
    • If the value is set to wildcard for fuzzy matching, then *Service: will be displayed. For example, if you set it to service:*sql, any field in the list that has service and ends with sql (for example: service=mysql; service=pymysql) will bind this inner view on the detail page of the explorer.

    Order of binding field display: service > app_id > source > project > label, the order of the same fields is not specially treated.

    • If service = ${value}, source = ${value}, project = ${value} match the same inner view, only this inner view is displayed on the explorer detail page
    • If service = ${value}, source = ${value}, project = ${value} match different inner views, the corresponding inner views are displayed in the order of service > source > project on the explorer detail page

    The inner view bound on the explorer details page, the default display time range is "the last 15 minutes", and the time of the current data record will be marked in the graph.

    Feedback

    Is this page helpful? ×