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

System architecture

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

Data Flow Process

OAgent is divided into the client layer, control platform, core service layer (agent base), OceanBase component access layer, and model inference layer from top to bottom. The knowledge base, as an independent knowledge supply unit, provides retrieval capabilities for the core service layer.

The system mainly consists of the following parts:

  • Client Layer

    Provides various entry points such as the console, web chat, CLI, and API to uniformly connect to the control platform. Among them, Control UI is the agent console for managing sessions, components, and system settings; Web Chat is the entry point for web-based dialogue and collaboration; CLI/API are aimed at automated and integrated invocation scenarios.

  • Control Platform

    Handles four types of management capabilities: tool and skill management (user-defined skills, tools, etc.), component management (managing basic component information), knowledge base management (user-defined knowledge bases and skills), and authentication security (access control, audit logging, observability). It routes requests to the core service layer via RPC/control plane interfaces.

  • Core Service Layer (Agent Base)

    Responsible for multi-agent collaboration, session and tools, knowledge and memory, model inference, and automated scheduling. Specifically includes:

    • Multi-agent Collaboration: General collaborative agents, OceanBase DBA agents, OceanBase Dev agents, etc., collaborate based on role division.

    • Session and Tools: Session routing and context management, skill and Skill orchestration, unified invocation of component capabilities and interfaces.

    • Knowledge and Memory: Manages OceanBase knowledge, component knowledge, and expert experience.

    • Scheduled Task Service: Manages scheduled tasks, schedules, and executes them.

  • OceanBase Component Access Layer

    Unifies the invocation of component capabilities and Skills through the control platform. It encapsulates the capabilities of components like OCP, OAS, and ODC into a unified component and tool (Skill/Tool) interface for the core service layer to call.

  • Knowledge Base

    Provides built-in knowledge such as OceanBase knowledge, component knowledge, and expert skills. It also supports integrating custom knowledge bases and custom skills, which are preferentially retrieved by the Agent before answering technical questions.

  • Model and Inference Layer

    Connects with various model providers (such as Qwen, DeepSeek, etc.) to provide model capabilities for agent inference and tool scheduling. OAgent does not have a built-in large language model; its inference capability is provided by external large language model APIs that you connect to. It supports the OpenAI-compatible Chat Completions interface and the OpenAI Responses API protocol. Model service providers and model lists are maintained on the Model Configuration page. For details, see Manage model services.

Data Flow Process

  1. A user initiates a natural language request in the client layer.

  2. The control platform completes authentication and routing, forwarding the request to the core service layer.

  3. The core service layer matches the appropriate agent and skill based on the request, orchestrates the required tool invocation, and retrieves knowledge from the knowledge base if needed.

  4. The component access layer accesses systems such as OCP, OAS, and ODC through REST APIs or the MCP (Model Context Protocol) interface to obtain cluster status and diagnostic data, or to perform change operations.

  5. The core service layer feeds the collected data and knowledge into model inference to generate user-oriented analysis conclusions and operational recommendations. It then returns the tool invocation process and results to the client for display.

Previous topic

Key features
Last

Next topic

Use cases
Next
on this page
Data Flow Process