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

Databases

OceanBase 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 Service

Connectors and Middleware

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

Databases

OceanBase 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 Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase Admin Tool

V4.1.2
  • What's new
  • Product introduction
    • What is OAT?
    • Architecture
    • Concepts
  • Quick start
    • Install OAT
    • Get started with OAT
  • oatcli
  • Upgrade guide
  • User guide
    • Log on to OAT
    • Page layout of the OAT console
    • Servers
      • Add a server
      • Edit a server
      • Perform O&M operations on a server
      • Remove a server
      • Manage credentials
    • Product services
      • Install, upgrade, and uninstall OCP
      • Install, upgrade, and uninstall ODC
      • Install, upgrade, and uninstall OMS
      • Install, Upgrade, Modify, and Uninstall OB Sharding
      • Create and uninstall MetaDB
      • Create and uninstall OBDNS
      • Create and uninstall InfluxDB
      • Create and uninstall NLB
      • Create and uninstall OpenSearch
      • Install and uninstall OBLB
      • Take over OCP
      • Take over ODC
      • Take over OB Sharding
      • Take over OMS
      • Take over MetaDB
      • Take over OBDNS
      • Take over InfluxDB
      • Take over NLB
      • Manage images
      • Modify resources of products and components
      • Manage tools
      • Data refresh
    • System security
      • Task list
      • Package management
      • Manage users
      • Operation audit
  • FAQ

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Admin Tool
  3. V4.1.2

Operation audit

Last Updated:2026-09-03 09:50:13

OceanBase Admin Toolkit (OAT) provides the operation audit feature to meet the security and compliance requirements. It records O&M operations performed in the OAT console in real time and allows you to query the operation records.

In the left-side navigation pane, choose System and Security > Operation Audit to go to the Operation Audit page. On the Operation Audit page, events are displayed on different pages, and you can filter them by time. By default, the Operation Audit displays the records in the last 24 hours. You can query the records in the last 24 hours, last 7 days, last 30 days, or a custom time range. You can also search for records by resource name. The Operation Audit page displays the following information:

  • Resource type You can filter records by resource type. By default, historical resources are retained for one year.

  • Resource operation

    Resource type
    Resource operation
    Component Create a component
    Uninstall a component
    Take over a component
    Modify a component
    Product Create a product
    Uninstall a product
    Take over a product
    Modify a product
    Upgrade a product
    Tool Create a tool
    Configure a tool
    Uninstall a tool
    Server Add a server
    Edit a server
    Delete a server
    Manage credentials Create credentials
    Modify credentials
    Delete credentials
    Package management Scan packages
    Delete a package
  • Resource name

    • The name of the resource involved in the operation, which can be the IP address of a server, a product name, or a component name.
    • If different types of resources, such as OCP, ODC, and OMS, are involved, the resource name is specified in type/name format, for example, OCP/MyOCP.
  • Operation information A JSON string that contains the operation request.

  • Operator The name of the user that initiated the operation. You can filter records by operator.

  • Source IP The IP address of the client that initiated the operation.

  • Execution time The start time of the operation. You can sort records by execution time. By default, the records are sorted in descending order of execution time.

  • Execution result The execution result of the operation, including Successful and Failed.

Previous topic

Manage users
Last

Next topic

FAQ
Next