作为一名与数据库密切相关且经验丰富的开发人员，在定位问题时，通常需要查看 OceanBase 实例。
在 OB Cloud 控制台中，用户可以查看 OceanBase 实例、租户、节点以及代理等信息。此外，控制台提供了多达几十甚至上百项的监控指标，用于观察是否存在异常情况。然而，用户往往需要通过逐级点击和逐步排查的方式进行定位。在某些情况下，用户还需要深入 OB Cloud 的诊断模块，排查 top sql、slow sql、可疑 sql 或高危 sql 等，以确定问题的可能位置。在经过上述两步操作后，通常还需继续深入数据库内部执行相关操作，进一步定位问题。此时，用户可能需要结合 OceanBase 官网文档查阅相关资料，以辅助思考并确定可能的搜索方向，从而定位问题。
回顾上述交互流程，可以看到一些问题（局限性）。
OB Cloud 管控台的 UI 界面，是面向所有用户的一个“通用性”的交互方案，为了满足信息架构的逻辑性，难免会牺牲操作的便捷性，举例来说，你的操作路径总是：
选择 obcloud 实例 -> 选择租户 -> 查看监控 -> 切换监控指标 -> 查看租户诊断 -> 筛选诊断信息
选择 obcloud 实例 -> 选择租户 -> 选择 unit -> 查看 unit 监控 -> 切换监控指标
在官网查文档则可以视为另一个重复的交互过程，直接查阅不可能命中你想要的答案，总是需要多次浏览、阅读文档，才能找到可能有效的方案。
从交互和查阅两个方面来看，用户实际上花费了大量时间在这些重复的操作上，而日常运维工作往往也遵循类似的流程。尽管在实际工作中，遇到问题的概率相对较小，很多时候用户只是想检查当前运行的实例和数据库是否存在异常，但完成这样一套重复的操作仍会耗费大量时间。
前端视角下 AI 为运维带来的变化和挑战
随着人工智能技术的兴起，尤其是近一年来 AI 的广泛应用，人们在遇到问题时的反应发生了显著变化。以往，人们可能会首先通过搜索引擎查找答案，而现在，他们更倾向于直接向 AI 助手（如DeepSeek）提问。
这是因为 AI 能够更高效地理解用户意图，并基于该意图整合出更符合用户需求的答案，从而在大多数场景下消除许多无效的交互过程。例如，当用户询问“牛肉怎么做才好吃”时，AI 能够准确地提供答案，而如果通过搜索引擎查找，用户可能需要浏览多个标题，甚至将多个来源的信息拼凑在一起才能找到满意的答案。
那么，AI可以为传统运维带来哪些改变？
AI替代传统GUI：OB Cloud MCP
在 AI 时代的人机交互中，数据才是核心要素。图形用户界面（GUI）的存在主要是为了帮助人们更好地理解数据。结合AI技术，我们可以利用大模型替代传统的图形界面，帮助用户理解数据。
https://avg.163.com/topic/detail/13147348
https://avg.163.com/topic/detail/13147353
https://avg.163.com/topic/detail/13147570
https://avg.163.com/topic/detail/13147350
https://avg.163.com/topic/detail/13147355
https://avg.163.com/topic/detail/13147374
https://avg.163.com/topic/detail/13147574
https://avg.163.com/topic/detail/13147349
https://avg.163.com/topic/detail/13147354
https://avg.163.com/topic/detail/13147380
https://avg.163.com/topic/detail/13147577
https://avg.163.com/topic/detail/13147347
https://avg.163.com/topic/detail/13147352
https://avg.163.com/topic/detail/13147524
https://avg.163.com/topic/detail/13147624
https://avg.163.com/topic/detail/13147341
https://avg.163.com/topic/detail/13147346
https://avg.163.com/topic/detail/13147351
https://avg.163.com/topic/detail/13147506
https://avg.163.com/topic/detail/13147615
https://avg.163.com/topic/detail/13147341
https://avg.163.com/topic/detail/13149721
https://avg.163.com/topic/detail/13149850
https://avg.163.com/topic/detail/13150013
https://avg.163.com/topic/detail/13150158
https://avg.163.com/topic/detail/13150293
https://avg.163.com/topic/detail/13149719
https://avg.163.com/topic/detail/13149855
https://avg.163.com/topic/detail/13150015
https://avg.163.com/topic/detail/13150159
https://avg.163.com/topic/detail/13150298
https://avg.163.com/topic/detail/13149715
https://avg.163.com/topic/detail/13149902
https://avg.163.com/topic/detail/13150004
https://avg.163.com/topic/detail/13150153
https://avg.163.com/topic/detail/13150291
https://avg.163.com/topic/detail/13149740
https://avg.163.com/topic/detail/13149870
https://avg.163.com/topic/detail/13150029
https://avg.163.com/topic/detail/13150175
https://avg.163.com/topic/detail/13150317
https://avg.163.com/topic/detail/13158390
https://avg.163.com/topic/detail/13158388
https://avg.163.com/topic/detail/13158486
https://avg.163.com/topic/detail/13158482
https://avg.163.com/topic/detail/13158658
https://avg.163.com/topic/detail/13158652
https://avg.163.com/topic/detail/13158765
https://avg.163.com/topic/detail/13158748
https://avg.163.com/topic/detail/13158888
https://avg.163.com/topic/detail/13158883
https://avg.163.com/topic/detail/13158391
https://avg.163.com/topic/detail/13158489
https://avg.163.com/topic/detail/13158660
https://avg.163.com/topic/detail/13158758
https://avg.163.com/topic/detail/13158885
https://avg.163.com/topic/detail/13158385
https://avg.163.com/topic/detail/13158506
https://avg.163.com/topic/detail/13158650
https://avg.163.com/topic/detail/13158745
https://avg.163.com/topic/detail/13158879
https://avg.163.com/topic/detail/13158386
https://avg.163.com/topic/detail/13158656
https://avg.163.com/topic/detail/13158760
https://avg.163.com/topic/detail/13158891
https://avg.163.com/topic/detail/13158380
https://avg.163.com/topic/detail/13158500
https://avg.163.com/topic/detail/13158646
https://avg.163.com/topic/detail/13158743
https://avg.163.com/topic/detail/13158899
