OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase AI DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog ServiceOceanBase DataPilotOceanBase OAgent

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase AI DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog ServiceOceanBase DataPilotOceanBase OAgent
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase OAgent

V2.2.0
  • Product overview
    • What is OAgent?
    • Key features
    • System architecture
    • Use cases
  • Quick start
  • Deployment
  • Overview
  • Sessions and diagnosis
    • Manage sessions
    • Switch dialogue models
    • Use @ to mention the analysis target
    • View the tool invocation process
    • Upload an attachment
    • Data visualization
    • FAQ
    • Export a report
  • Tools
  • Skill Management
  • Channel management
  • Knowledge base
    • Built-in knowledge base
    • Custom knowledge base
  • Scheduled tasks
    • Overview of scheduled tasks
    • Create a scheduled task
  • View usage
  • Model configuration
    • Manage model services
    • Model scoring
  • Settings and security
    • Product management
    • Experimental features
  • Best practices
    • Perform a cluster health inspection
    • Query cluster and topology information
    • Query resource metrics and task status
    • Read-only queries
    • Alert query and troubleshooting guide
    • Root cause analysis of exceptions
    • ASH diagnostic report
    • Analyze slow SQL, TopSQL, and abnormal SQL
    • SQL pre-analysis and tuning recommendations
    • Interpret execution plans
    • Diagnostic information statistics
    • Parameter check and change governance
    • Database change ticket
  • Appendix
    • Feature list
    • Built-in Skills
  • Release notes
    • OAgent V2.2.0 Release note
    • OAgent V2.1.0 Release note
    • OAgent V2.0.0 Release note
    • OAgent V1.8.0 Release note

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase OAgent
  3. V2.2.0

Use @ to mention the analysis target

Last Updated:2026-11-20 07:25:11

Prerequisites
Procedure
Suggestions

When asking questions, you can use the @ shortcut to select the component, cluster, or tenant you want to analyze. The Agent will automatically complete parameters such as clusterId, clusterName, and tenantId required for the tool call, avoiding errors from manual entry.

Prerequisites

You have completed the configuration of an OCP/OAS product connection. For details, see Create a product connection.

Procedure

  1. Enter @ in the session input box, or click the @ button below the input box.

  2. In the pop-up list, select the target product (component), for example, OCP_TEST.

  3. The system expands the list of clusters under this product. Select the target cluster. A dot before the cluster name indicates the current running status of the cluster.

    Press Tab to quickly confirm the currently highlighted item. If you need to drill down to a tenant, you can select the target tenant from the list after selecting the cluster.

  4. Add the requirement for this analysis (for example, "Help me inspect this cluster") and press Enter to send it.

Suggestions

  • For diagnostic questions involving specific clusters or tenants (inspection, slow SQL, alerts, ASH, statistics, etc.), it is recommended to specify the target using @. This way, the Agent does not need to ask for the cluster name again, reducing one round of interaction.

  • After specifying a target using @ for the first time in the same session, subsequent questions will continue this context. If you need to switch the analysis target, just use @ to select a new one.

  • If you only need to query the list of clusters or component information under a certain product, you can directly mention the product name in your question, for example, "What clusters are there in OCP_TEST?".

Previous topic

Switch dialogue models
Last

Next topic

View the tool invocation process
Next
on this page
Prerequisites
Procedure
Suggestions