[{"data":1,"prerenderedAt":790},["ShallowReactive",2],{"\u002Fzh\u002Fblogs\u002F202508071":3,"content-doc-\u002Fen\u002Fblogs\u002F202508071":415,"surround-\u002Fen\u002Fblogs\u002F202508071":788},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"date":10,"category":11,"author":12,"body":16,"_type":407,"_id":408,"_source":409,"_file":410,"_stem":411,"_extension":412,"coverImage":109,"plainText":413,"authorNames":414},"\u002Fzh\u002Fblogs\u002F202508071","blogs",false,"","openUBMC可观测技术：洞察系统全貌、引领BMC新视界","在数字化转型的浪潮中，系统复杂性与日俱增，如何高效监控和管理分布式系统成为关键挑战。BMC系统（Baseboard Management Controller，基板管理控制器）作为硬件与软件之间的桥梁，承担着设备管理、监控和维护的重要职责。为了提升openUBMC的可观测性，在25.06版本中我们构建了observability组件，基于openTelemetry构建了完整的可观测能力，帮助开发者更清晰地洞察系统运行状态，快速定位问题，优化系统性能。","2025\u002F08\u002F07","essentials",[13],{"name":14,"description":15},"许强","openUBMC Interface SIG Maintainer，专注提升openUBMC接口管理效率和BMC固件可定位性。",{"type":17,"children":18,"toc":390},"root",[19,27,32,37,44,51,56,102,111,117,122,151,158,164,169,176,182,187,193,198,203,266,272,277,333,339,345,350,355,361,366,379],{"type":20,"tag":21,"props":22,"children":24},"element","h1",{"id":23},"openubmc可观测技术洞察系统全貌引领bmc新视界",[25],{"type":26,"value":8},"text",{"type":20,"tag":28,"props":29,"children":30},"p",{},[31],{"type":26,"value":9},{"type":20,"tag":28,"props":33,"children":34},{},[35],{"type":26,"value":36},"本文将详细介绍openUBMC可观测能力的优势、价值以及未来展望，期待开发者共同参与openUBMC可观测能力的建设。",{"type":20,"tag":38,"props":39,"children":41},"h2",{"id":40},"一openubmc可观测能力的优势",[42],{"type":26,"value":43},"一、openUBMC可观测能力的优势",{"type":20,"tag":45,"props":46,"children":48},"h3",{"id":47},"_1-统一的数据采集与管理",[49],{"type":26,"value":50},"1. 统一的数据采集与管理",{"type":20,"tag":28,"props":52,"children":53},{},[54],{"type":26,"value":55},"openUBMC通过openTelemetry实现了对指标、日志和跟踪数据的统一采集和管理。无论是硬件状态、系统性能，还是软件运行情况，所有数据都被整合上报到统一的平台中，确保数据的完整性和一致性。",{"type":20,"tag":57,"props":58,"children":59},"ul",{},[60,76,89],{"type":20,"tag":61,"props":62,"children":63},"li",{},[64,70,74],{"type":20,"tag":65,"props":66,"children":67},"strong",{},[68],{"type":26,"value":69},"标准编程接口",{"type":20,"tag":71,"props":72,"children":73},"br",{},[],{"type":26,"value":75},"\nopenUBMC基于openTelemetry封装和提供了应用框架编程接口，简化了数据采集的实现。开发者可以通过简单的API调用，轻松地将遥测数据集成到BMC系统中。",{"type":20,"tag":61,"props":77,"children":78},{},[79,84,87],{"type":20,"tag":65,"props":80,"children":81},{},[82],{"type":26,"value":83},"标准数据格式",{"type":20,"tag":71,"props":85,"children":86},{},[],{"type":26,"value":88},"\n统一的遥测数据格式，包括指标（Metrics）、日志（Logs）和跟踪（Traces），这些格式确保了不同数据源之间的兼容性和一致性，便于后续的数据处理和分析。",{"type":20,"tag":61,"props":90,"children":91},{},[92,97,100],{"type":20,"tag":65,"props":93,"children":94},{},[95],{"type":26,"value":96},"标准传输协议",{"type":20,"tag":71,"props":98,"children":99},{},[],{"type":26,"value":101},"\n采用openTelemetry传输协议，包括gRPC和HTTP\u002FJSON。gRPC适用于高性能场景，提供高效的数据传输；HTTP\u002FJSON则提供了良好的兼容性，便于与现有系统和工具集成。",{"type":20,"tag":28,"props":103,"children":104},{},[105],{"type":20,"tag":106,"props":107,"children":110},"img",{"alt":108,"src":109},"images","\u002Fcategory\u002Fblog\u002F20250807\u002Fimg01.gif",[],{"type":20,"tag":45,"props":112,"children":114},{"id":113},"_2-与主流工具的无缝集成",[115],{"type":26,"value":116},"2. 与主流工具的无缝集成",{"type":20,"tag":28,"props":118,"children":119},{},[120],{"type":26,"value":121},"借助openTelemetry Collector，openUBMC的可观测能力支持与Prometheus、Zipkin、Jaeger、ELK等工具无缝集成，提供强大的数据可视化和分析能力，帮助用户更好地理解和优化系统性能。",{"type":20,"tag":57,"props":123,"children":124},{},[125,138],{"type":20,"tag":61,"props":126,"children":127},{},[128,133,136],{"type":20,"tag":65,"props":129,"children":130},{},[131],{"type":26,"value":132},"数据采集与处理",{"type":20,"tag":71,"props":134,"children":135},{},[],{"type":26,"value":137},"\nopenTelemetry Collector支持多种数据格式和协议，能够灵活地处理从各个数据源采集的遥测数据（指标、日志、跟踪）。",{"type":20,"tag":61,"props":139,"children":140},{},[141,146,149],{"type":20,"tag":65,"props":142,"children":143},{},[144],{"type":26,"value":145},"数据转换与导出",{"type":20,"tag":71,"props":147,"children":148},{},[],{"type":26,"value":150},"\nopenTelemetry Collector能够对采集到的数据进行转换和导出到多个目标系统，如Prometheus、Grafana、Jaeger等。这种多目标导出能力，使得BMC系统的可观测数据能够被多个工具同时利用，提升数据的利用率。",{"type":20,"tag":28,"props":152,"children":153},{},[154],{"type":20,"tag":106,"props":155,"children":157},{"alt":108,"src":156},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg02.webp",[],{"type":20,"tag":45,"props":159,"children":161},{"id":160},"_3-强大的分布式追踪能力",[162],{"type":26,"value":163},"3. 强大的分布式追踪能力",{"type":20,"tag":28,"props":165,"children":166},{},[167],{"type":26,"value":168},"借助Zipkin等平台的可视化分析能力，openUBMC能够清晰地展示完整调用路径。开发者可以轻松追踪从硬件到软件的每一个操作，快速定位性能瓶颈和故障点。",{"type":20,"tag":28,"props":170,"children":171},{},[172],{"type":20,"tag":106,"props":173,"children":175},{"alt":108,"src":174},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg03.webp",[],{"type":20,"tag":45,"props":177,"children":179},{"id":178},"_4-高可扩展性和灵活性",[180],{"type":26,"value":181},"4. 高可扩展性和灵活性",{"type":20,"tag":28,"props":183,"children":184},{},[185],{"type":26,"value":186},"openUBMC提供的应用框架编程接口，使得可观测能力具有高度的可扩展性。开发者可以根据需求定制数据采集和处理逻辑，满足不同场景下的观测需求。",{"type":20,"tag":38,"props":188,"children":190},{"id":189},"二openubmc可观测能力的价值",[191],{"type":26,"value":192},"二、openUBMC可观测能力的价值",{"type":20,"tag":28,"props":194,"children":195},{},[196],{"type":26,"value":197},"数据驱动价值——通过实时监控硬件与软件运行状态，汇聚分析数据可精准识别系统瓶颈与潜在风险。定向数据采集更能快速定位异常，在研发阶段提前识别异常，有效预防故障发生，从而全面提升系统稳定性与可靠性。",{"type":20,"tag":28,"props":199,"children":200},{},[201],{"type":26,"value":202},"故障定位时，清晰的调用链路与精准的性能数据可帮助开发者迅速定界问题范围，精准溯源根因，大幅缩短故障修复周期。以下是25.06版本研发时使用Observability组件识别出来的问题案例：",{"type":20,"tag":57,"props":204,"children":205},{},[206,226,246],{"type":20,"tag":61,"props":207,"children":208},{},[209,214,217,219,222],{"type":20,"tag":65,"props":210,"children":211},{},[212],{"type":26,"value":213},"FLASH日志刷屏问题",{"type":20,"tag":71,"props":215,"children":216},{},[],{"type":26,"value":218},"\n通过监控FLASH写入量，分析增长趋势，即可提前识别和拦截写入量过大导致的flash寿命受损问题。",{"type":20,"tag":71,"props":220,"children":221},{},[],{"type":20,"tag":106,"props":223,"children":225},{"alt":108,"src":224},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg04.webp",[],{"type":20,"tag":61,"props":227,"children":228},{},[229,234,237,239,242],{"type":20,"tag":65,"props":230,"children":231},{},[232],{"type":26,"value":233},"硬件访问故障问题",{"type":20,"tag":71,"props":235,"children":236},{},[],{"type":26,"value":238},"\n选取监控硬件访问指标，并过滤硬件访问错误，通过观察硬件访问错误增长趋势，即可快速锁定故障硬件。",{"type":20,"tag":71,"props":240,"children":241},{},[],{"type":20,"tag":106,"props":243,"children":245},{"alt":108,"src":244},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg05.webp",[],{"type":20,"tag":61,"props":247,"children":248},{},[249,254,257,259,262],{"type":20,"tag":65,"props":250,"children":251},{},[252],{"type":26,"value":253},"CSR配置不合理问题",{"type":20,"tag":71,"props":255,"children":256},{},[],{"type":26,"value":258},"\n同样通过监控硬件访问指标，通过数据识别CSR中器件访问不合理\u002F错误的配置，从而优化整体硬件访问周期、提升整体BMC运行性能。",{"type":20,"tag":71,"props":260,"children":261},{},[],{"type":20,"tag":106,"props":263,"children":265},{"alt":108,"src":264},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg06.webp",[],{"type":20,"tag":38,"props":267,"children":269},{"id":268},"三未来展望携手共建openubmc可观测能力",[270],{"type":26,"value":271},"三、未来展望：携手共建openUBMC可观测能力",{"type":20,"tag":28,"props":273,"children":274},{},[275],{"type":26,"value":276},"openUBMC的可观测能力是开放的、可扩展的，我们欢迎更多的开发者和社区伙伴加入，共同完善和优化这一能力。未来，我们计划在以下几个方向上持续发力：",{"type":20,"tag":278,"props":279,"children":280},"ol",{},[281,294,307,320],{"type":20,"tag":61,"props":282,"children":283},{},[284,289,292],{"type":20,"tag":65,"props":285,"children":286},{},[287],{"type":26,"value":288},"增强硬件与软件的深度集成",{"type":20,"tag":71,"props":290,"children":291},{},[],{"type":26,"value":293},"\n深化硬件与软件的协同观测能力，提供更全面的设备管理视角。",{"type":20,"tag":61,"props":295,"children":296},{},[297,302,305],{"type":20,"tag":65,"props":298,"children":299},{},[300],{"type":26,"value":301},"引入AI驱动的异常检测",{"type":20,"tag":71,"props":303,"children":304},{},[],{"type":26,"value":306},"\n利用AI技术对观测数据进行智能分析，提前发现潜在问题。",{"type":20,"tag":61,"props":308,"children":309},{},[310,315,318],{"type":20,"tag":65,"props":311,"children":312},{},[313],{"type":26,"value":314},"构建开发者友好工具链",{"type":20,"tag":71,"props":316,"children":317},{},[],{"type":26,"value":319},"\n提供更多易用的工具和插件，降低开发者使用openUBMC可观测能力的门槛。",{"type":20,"tag":61,"props":321,"children":322},{},[323,328,331],{"type":20,"tag":65,"props":324,"children":325},{},[326],{"type":26,"value":327},"推动社区共建",{"type":20,"tag":71,"props":329,"children":330},{},[],{"type":26,"value":332},"\n通过技术分享、开源贡献等方式，与社区开发者共同完善openUBMC可观测能力。",{"type":20,"tag":38,"props":334,"children":336},{"id":335},"四总结",[337],{"type":26,"value":338},"四、总结",{"type":20,"tag":45,"props":340,"children":342},{"id":341},"洞察系统全貌引领bmc新视界",[343],{"type":26,"value":344},"“洞察系统全貌，引领BMC新视界”",{"type":20,"tag":28,"props":346,"children":347},{},[348],{"type":26,"value":349},"openUBMC的可观测能力基于openTelemetry构建，不仅提升了系统的稳定性和性能，还为开发者提供了一个高效、灵活的开发和观测平台。我们相信，通过社区和开发伙伴的共同努力，openUBMC的可观测能力将变得更加完善，为更多开发者和用户提供价值。",{"type":20,"tag":28,"props":351,"children":352},{},[353],{"type":26,"value":354},"如果你对openUBMC的可观测能力感兴趣，欢迎加入我们的社区，与我们一起探索和实践！让我们携手共建更智能、更可靠的BMC系统！",{"type":20,"tag":45,"props":356,"children":358},{"id":357},"加入我们共建openubmc可观测能力",[359],{"type":26,"value":360},"加入我们，共建openUBMC可观测能力！",{"type":20,"tag":28,"props":362,"children":363},{},[364],{"type":26,"value":365},"任何想法、问题，欢迎通过社区论坛、Issue、Interface SIG例会进行交流！",{"type":20,"tag":28,"props":367,"children":368},{},[369,371],{"type":26,"value":370},"Gitcode仓库：",{"type":20,"tag":372,"props":373,"children":377},"a",{"href":374,"rel":375},"https:\u002F\u002Fgitcode.com\u002FopenUBMC\u002Fobservability",[376],"nofollow",[378],{"type":26,"value":374},{"type":20,"tag":28,"props":380,"children":381},{},[382,384],{"type":26,"value":383},"社区论坛：",{"type":20,"tag":372,"props":385,"children":388},{"href":386,"rel":387},"https:\u002F\u002Fdiscuss.openubmc.cn",[376],[389],{"type":26,"value":386},{"title":7,"searchDepth":391,"depth":391,"links":392},4,[393,401,402,403],{"id":40,"depth":394,"text":43,"children":395},2,[396,398,399,400],{"id":47,"depth":397,"text":50},3,{"id":113,"depth":397,"text":116},{"id":160,"depth":397,"text":163},{"id":178,"depth":397,"text":181},{"id":189,"depth":394,"text":192},{"id":268,"depth":394,"text":271},{"id":335,"depth":394,"text":338,"children":404},[405,406],{"id":341,"depth":397,"text":344},{"id":357,"depth":397,"text":360},"markdown","content:zh:blogs:202508071.md","content","zh\u002Fblogs\u002F202508071.md","zh\u002Fblogs\u002F202508071","md","openUBMC可观测技术：洞察系统全貌、引领BMC新视界 在数字化转型的浪潮中，系统复杂性与日俱增，如何高效监控和管理分布式系统成为关键挑战。BMC系统（Baseboard Management Controller，基板管理控制器）作为硬件与软件之间的桥梁，承担着设备管理、监控和维护的重要职责。为了提升openUBMC的可观测性，在25.06版本中我们构建了observability组件，基于openTelemetry构建了完整的可观测能力，帮助开发者更清晰地洞察系统运行状态，快速定位问题，优化系统性能。 本文将详细介绍openUBMC可观测能力的优势、价值以及未来展望，期待开发者共同参与openUBMC可观测能力的建设。 一、openUBMC可观测能力的优势 1. 统一的数据采集与管理 openUBMC通过openTelemetry实现了对指标、日志和跟踪数据的统一采集和管理。无论是硬件状态、系统性能，还是软件运行情况，所有数据都被整合上报到统一的平台中，确保数据的完整性和一致性。 标准编程接口  \nopenUBMC基于openTelemetry封装和提供了应用框架编程接口，简化了数据采集的实现。开发者可以通过简单的API调用，轻松地将遥测数据集成到BMC系统中。 标准数据格式  \n统一的遥测数据格式，包括指标（Metrics）、日志（Logs）和跟踪（Traces），这些格式确保了不同数据源之间的兼容性和一致性，便于后续的数据处理和分析。 标准传输协议  \n采用openTelemetry传输协议，包括gRPC和HTTP\u002FJSON。gRPC适用于高性能场景，提供高效的数据传输；HTTP\u002FJSON则提供了良好的兼容性，便于与现有系统和工具集成。  2. 与主流工具的无缝集成 借助openTelemetry Collector，openUBMC的可观测能力支持与Prometheus、Zipkin、Jaeger、ELK等工具无缝集成，提供强大的数据可视化和分析能力，帮助用户更好地理解和优化系统性能。 数据采集与处理  \nopenTelemetry Collector支持多种数据格式和协议，能够灵活地处理从各个数据源采集的遥测数据（指标、日志、跟踪）。 数据转换与导出  \nopenTelemetry Collector能够对采集到的数据进行转换和导出到多个目标系统，如Prometheus、Grafana、Jaeger等。这种多目标导出能力，使得BMC系统的可观测数据能够被多个工具同时利用，提升数据的利用率。  3. 强大的分布式追踪能力 借助Zipkin等平台的可视化分析能力，openUBMC能够清晰地展示完整调用路径。开发者可以轻松追踪从硬件到软件的每一个操作，快速定位性能瓶颈和故障点。  4. 高可扩展性和灵活性 openUBMC提供的应用框架编程接口，使得可观测能力具有高度的可扩展性。开发者可以根据需求定制数据采集和处理逻辑，满足不同场景下的观测需求。 二、openUBMC可观测能力的价值 数据驱动价值——通过实时监控硬件与软件运行状态，汇聚分析数据可精准识别系统瓶颈与潜在风险。定向数据采集更能快速定位异常，在研发阶段提前识别异常，有效预防故障发生，从而全面提升系统稳定性与可靠性。 故障定位时，清晰的调用链路与精准的性能数据可帮助开发者迅速定界问题范围，精准溯源根因，大幅缩短故障修复周期。以下是25.06版本研发时使用Observability组件识别出来的问题案例： FLASH日志刷屏问题  \n通过监控FLASH写入量，分析增长趋势，即可提前识别和拦截写入量过大导致的flash寿命受损问题。   硬件访问故障问题  \n选取监控硬件访问指标，并过滤硬件访问错误，通过观察硬件访问错误增长趋势，即可快速锁定故障硬件。   CSR配置不合理问题  \n同样通过监控硬件访问指标，通过数据识别CSR中器件访问不合理\u002F错误的配置，从而优化整体硬件访问周期、提升整体BMC运行性能。   三、未来展望：携手共建openUBMC可观测能力 openUBMC的可观测能力是开放的、可扩展的，我们欢迎更多的开发者和社区伙伴加入，共同完善和优化这一能力。未来，我们计划在以下几个方向上持续发力： 增强硬件与软件的深度集成  \n深化硬件与软件的协同观测能力，提供更全面的设备管理视角。 引入AI驱动的异常检测  \n利用AI技术对观测数据进行智能分析，提前发现潜在问题。 构建开发者友好工具链  \n提供更多易用的工具和插件，降低开发者使用openUBMC可观测能力的门槛。 推动社区共建  \n通过技术分享、开源贡献等方式，与社区开发者共同完善openUBMC可观测能力。 四、总结 “洞察系统全貌，引领BMC新视界” openUBMC的可观测能力基于openTelemetry构建，不仅提升了系统的稳定性和性能，还为开发者提供了一个高效、灵活的开发和观测平台。我们相信，通过社区和开发伙伴的共同努力，openUBMC的可观测能力将变得更加完善，为更多开发者和用户提供价值。 如果你对openUBMC的可观测能力感兴趣，欢迎加入我们的社区，与我们一起探索和实践！让我们携手共建更智能、更可靠的BMC系统！ 加入我们，共建openUBMC可观测能力！ 任何想法、问题，欢迎通过社区论坛、Issue、Interface SIG例会进行交流！ Gitcode仓库： https:\u002F\u002Fgitcode.com\u002FopenUBMC\u002Fobservability 社区论坛： https:\u002F\u002Fdiscuss.openubmc.cn",[14],{"_path":416,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":417,"description":418,"date":10,"category":11,"author":419,"body":422,"_type":407,"_id":783,"_source":409,"_file":784,"_stem":785,"_extension":412,"coverImage":502,"plainText":786,"authorNames":787},"\u002Fen\u002Fblogs\u002F202508071","openUBMC Observability: Full Insight into the System for a New BMC Vision","As digital transformation surges forward, system complexities escalate continuously. The efficient monitoring and management of distributed systems have become a key challenge. As a bridge between hardware and software, the baseboard management controller (BMC) is responsible for device management, monitoring, and maintenance. openUBMC 25.06 introduces the Observability component to provide complete observability capabilities based on openTelemetry, enabling developers to clearly understand system status, quickly locate issues, and optimize system performance.",[420],{"name":14,"description":421},"openUBMC Interface SIG maintainer, focusing on enhancing interface management efficiency and optimizing BMC firmware locating.",{"type":17,"children":423,"toc":769},[424,429,433,438,444,450,455,497,504,510,515,538,545,551,556,563,569,574,580,585,590,650,656,661,716,722,728,733,738,744,749,759],{"type":20,"tag":21,"props":425,"children":427},{"id":426},"openubmc-observability-full-insight-into-the-system-for-a-new-bmc-vision",[428],{"type":26,"value":417},{"type":20,"tag":28,"props":430,"children":431},{},[432],{"type":26,"value":418},{"type":20,"tag":28,"props":434,"children":435},{},[436],{"type":26,"value":437},"This article explores the advantages, value, and prospects of openUBMC Observability. We look forward to your participation in the capability development of openUBMC Observability.",{"type":20,"tag":38,"props":439,"children":441},{"id":440},"advantages",[442],{"type":26,"value":443},"Advantages",{"type":20,"tag":45,"props":445,"children":447},{"id":446},"_1-unified-data-collection-and-management",[448],{"type":26,"value":449},"1. Unified Data Collection and Management",{"type":20,"tag":28,"props":451,"children":452},{},[453],{"type":26,"value":454},"openUBMC uses openTelemetry to implement unified collection and management of metrics, logs, and traces. All data, including hardware status, system performance, and software status, is integrated and reported to openUBMC to ensure data integrity and consistency.",{"type":20,"tag":57,"props":456,"children":457},{},[458,471,484],{"type":20,"tag":61,"props":459,"children":460},{},[461,466,469],{"type":20,"tag":65,"props":462,"children":463},{},[464],{"type":26,"value":465},"Standard programming APIs",{"type":20,"tag":71,"props":467,"children":468},{},[],{"type":26,"value":470},"\nopenUBMC encapsulates and provides application programming interfaces (APIs) based on openTelemetry to simplify data collection. Developers can easily integrate telemetry data into the BMC system through simple API calls.",{"type":20,"tag":61,"props":472,"children":473},{},[474,479,482],{"type":20,"tag":65,"props":475,"children":476},{},[477],{"type":26,"value":478},"Standard data formats",{"type":20,"tag":71,"props":480,"children":481},{},[],{"type":26,"value":483},"\nThe unified telemetry framework defines compatible and consistent formats for metrics, logs, and traces, facilitating subsequent data processing and analysis.",{"type":20,"tag":61,"props":485,"children":486},{},[487,492,495],{"type":20,"tag":65,"props":488,"children":489},{},[490],{"type":26,"value":491},"Standard transmission protocols",{"type":20,"tag":71,"props":493,"children":494},{},[],{"type":26,"value":496},"\nopenTelemetry Protocol (OTLP) is used, supporting both gRPC and HTTP\u002FJSON. gRPC is applicable to high-performance scenarios for efficient data transfer. HTTP\u002FJSON provides wide compatibility, facilitating integration with existing systems and tools.",{"type":20,"tag":28,"props":498,"children":499},{},[500],{"type":20,"tag":106,"props":501,"children":503},{"alt":108,"src":502},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg01-en.png",[],{"type":20,"tag":45,"props":505,"children":507},{"id":506},"_2-seamless-integration-with-mainstream-tools",[508],{"type":26,"value":509},"2. Seamless Integration with Mainstream Tools",{"type":20,"tag":28,"props":511,"children":512},{},[513],{"type":26,"value":514},"openTelemetry Collector allows openUBMC Observability to seamlessly integrate with tools such as Prometheus, Zipkin, Jaeger, and Elasticsearch, Logstash, and Kibana (ELK). In this way, powerful data visualization and analysis capabilities are provided to help users better understand and optimize system performance.",{"type":20,"tag":57,"props":516,"children":517},{},[518,528],{"type":20,"tag":61,"props":519,"children":520},{},[521,526],{"type":20,"tag":65,"props":522,"children":523},{},[524],{"type":26,"value":525},"Data collection and processing",{"type":26,"value":527},"\nopenTelemetry Collector supports multiple data formats and protocols, and can flexibly process telemetry data (metrics, logs, and traces) from various data sources.",{"type":20,"tag":61,"props":529,"children":530},{},[531,536],{"type":20,"tag":65,"props":532,"children":533},{},[534],{"type":26,"value":535},"Data conversion and export",{"type":26,"value":537},"\nopenTelemetry Collector can convert collected data and export it to different target systems, such as Prometheus, Grafana, and Jaeger. This enables the observability data from the BMC to be simultaneously used by multiple tools, thereby improving data utilization.",{"type":20,"tag":28,"props":539,"children":540},{},[541],{"type":20,"tag":106,"props":542,"children":544},{"alt":108,"src":543},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg02-en.png",[],{"type":20,"tag":45,"props":546,"children":548},{"id":547},"_3-powerful-distributed-tracing-capability",[549],{"type":26,"value":550},"3. Powerful Distributed Tracing Capability",{"type":20,"tag":28,"props":552,"children":553},{},[554],{"type":26,"value":555},"With the visualized analysis capability of platforms such as Zipkin, openUBMC can clearly display the complete call paths. Developers can easily trace every operation from hardware to software, and thus quickly locate performance bottlenecks and faults.",{"type":20,"tag":28,"props":557,"children":558},{},[559],{"type":20,"tag":106,"props":560,"children":562},{"alt":108,"src":561},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg03-en.png",[],{"type":20,"tag":45,"props":564,"children":566},{"id":565},"_4-high-scalability-and-flexibility",[567],{"type":26,"value":568},"4. High Scalability and Flexibility",{"type":20,"tag":28,"props":570,"children":571},{},[572],{"type":26,"value":573},"openUBMC provides APIs to support highly scalable observability. Developers can customize data collection and processing logic as required to meet observation requirements in different scenarios.",{"type":20,"tag":38,"props":575,"children":577},{"id":576},"value",[578],{"type":26,"value":579},"Value",{"type":20,"tag":28,"props":581,"children":582},{},[583],{"type":26,"value":584},"Data-driven benefits: By monitoring the hardware and software status in real time, openUBMC aggregates and analyzes data to accurately identify performance bottlenecks and potential risks. With targeted data collection, it identifies and locates anomalies early in the development phase, effectively preventing failures and enhancing overall system stability and reliability.",{"type":20,"tag":28,"props":586,"children":587},{},[588],{"type":26,"value":589},"During fault locating, clear call traces and accurate performance data enable developers to quickly define the fault scope, accurately trace the root cause, and significantly shorten the fault rectification time. The following issues were identified using the observability component during the R&D of the 25.06 version:",{"type":20,"tag":57,"props":591,"children":592},{},[593,613,630],{"type":20,"tag":61,"props":594,"children":595},{},[596,601,604,606,609],{"type":20,"tag":65,"props":597,"children":598},{},[599],{"type":26,"value":600},"Flash log flooding",{"type":20,"tag":71,"props":602,"children":603},{},[],{"type":26,"value":605},"\nBy monitoring the flash write volume and analyzing its growth trend, openUBMC detected and prevented flash lifespan degradation caused by excessive writes.",{"type":20,"tag":71,"props":607,"children":608},{},[],{"type":20,"tag":106,"props":610,"children":612},{"alt":108,"src":611},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg04-en.png",[],{"type":20,"tag":61,"props":614,"children":615},{},[616,621,623,626],{"type":20,"tag":65,"props":617,"children":618},{},[619],{"type":26,"value":620},"Hardware access failure",{"type":26,"value":622},"\nBy monitoring hardware access metrics and filtering access errors, openUBMC detected and prevented faulty hardware through the error growth trend analysis.",{"type":20,"tag":71,"props":624,"children":625},{},[],{"type":20,"tag":106,"props":627,"children":629},{"alt":108,"src":628},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg05-en.png",[],{"type":20,"tag":61,"props":631,"children":632},{},[633,638,641,643,646],{"type":20,"tag":65,"props":634,"children":635},{},[636],{"type":26,"value":637},"Improper CSR configuration",{"type":20,"tag":71,"props":639,"children":640},{},[],{"type":26,"value":642},"\nBy monitoring hardware access metrics and analyzing the collected data, openUBMC detected and prevented improper or invalid device access configurations in the CSR, optimizing hardware access cycles and improving overall BMC performance.",{"type":20,"tag":71,"props":644,"children":645},{},[],{"type":20,"tag":106,"props":647,"children":649},{"alt":108,"src":648},"\u002Fcategory\u002Fblog\u002F20250807\u002Fimg06-en.png",[],{"type":20,"tag":38,"props":651,"children":653},{"id":652},"prospects-jointly-building-openubmc-observability",[654],{"type":26,"value":655},"Prospects: Jointly Building openUBMC Observability",{"type":20,"tag":28,"props":657,"children":658},{},[659],{"type":26,"value":660},"openUBMC Observability is open and extensible. We welcome more developers and community partners to join us in improving and optimizing the capability. Looking ahead, we will continue focusing our efforts on the following key areas:",{"type":20,"tag":278,"props":662,"children":663},{},[664,677,690,703],{"type":20,"tag":61,"props":665,"children":666},{},[667,672,675],{"type":20,"tag":65,"props":668,"children":669},{},[670],{"type":26,"value":671},"Enhance deep integration of hardware and software.",{"type":20,"tag":71,"props":673,"children":674},{},[],{"type":26,"value":676},"\nDeepen the collaborative observability between hardware and software to provide a more comprehensive device management perspective.",{"type":20,"tag":61,"props":678,"children":679},{},[680,685,688],{"type":20,"tag":65,"props":681,"children":682},{},[683],{"type":26,"value":684},"Introduce AI-driven anomaly detection.",{"type":20,"tag":71,"props":686,"children":687},{},[],{"type":26,"value":689},"\nUse AI technologies to intelligently analyze observed data and detect potential issues in advance.",{"type":20,"tag":61,"props":691,"children":692},{},[693,698,701],{"type":20,"tag":65,"props":694,"children":695},{},[696],{"type":26,"value":697},"Building a developer-friendly tool chain",{"type":20,"tag":71,"props":699,"children":700},{},[],{"type":26,"value":702},"\nProvide more easy-to-use tools and plug-ins to lower the barrier for developers to use openUBMC Observability.",{"type":20,"tag":61,"props":704,"children":705},{},[706,711,714],{"type":20,"tag":65,"props":707,"children":708},{},[709],{"type":26,"value":710},"Promoting community co-construction",{"type":20,"tag":71,"props":712,"children":713},{},[],{"type":26,"value":715},"\nWork with community developers to improve openUBMC Observability through technical sharing and open source contributions.",{"type":20,"tag":38,"props":717,"children":719},{"id":718},"summary",[720],{"type":26,"value":721},"Summary",{"type":20,"tag":45,"props":723,"children":725},{"id":724},"full-insight-into-the-system-for-a-new-bmc-vision",[726],{"type":26,"value":727},"Full Insight into the System for a New BMC Vision",{"type":20,"tag":28,"props":729,"children":730},{},[731],{"type":26,"value":732},"openUBMC Observability is built based on openTelemetry. It not only improves system stability and performance, but also provides developers with an efficient and flexible platform for development and observation. We believe that through the joint efforts of the community and partners, openUBMC Observability will become more comprehensive and deliver more benefits to developers and users.",{"type":20,"tag":28,"props":734,"children":735},{},[736],{"type":26,"value":737},"If you are interested in openUBMC Observability, we warmly invite you to join our community. Let's explore and build a smarter, more reliable BMC system.",{"type":20,"tag":45,"props":739,"children":741},{"id":740},"join-us-to-build-openubmc-observability",[742],{"type":26,"value":743},"Join Us to Build openUBMC Observability",{"type":20,"tag":28,"props":745,"children":746},{},[747],{"type":26,"value":748},"You are welcome to share your ideas and questions through the community forum, submit issues, or join Interface SIG regular meetings.",{"type":20,"tag":28,"props":750,"children":751},{},[752,754],{"type":26,"value":753},"GitCode repository: ",{"type":20,"tag":372,"props":755,"children":757},{"href":374,"rel":756},[376],[758],{"type":26,"value":374},{"type":20,"tag":28,"props":760,"children":761},{},[762,764],{"type":26,"value":763},"Community forum: ",{"type":20,"tag":372,"props":765,"children":767},{"href":386,"rel":766},[376],[768],{"type":26,"value":386},{"title":7,"searchDepth":391,"depth":391,"links":770},[771,777,778,779],{"id":440,"depth":394,"text":443,"children":772},[773,774,775,776],{"id":446,"depth":397,"text":449},{"id":506,"depth":397,"text":509},{"id":547,"depth":397,"text":550},{"id":565,"depth":397,"text":568},{"id":576,"depth":394,"text":579},{"id":652,"depth":394,"text":655},{"id":718,"depth":394,"text":721,"children":780},[781,782],{"id":724,"depth":397,"text":727},{"id":740,"depth":397,"text":743},"content:en:blogs:202508071.md","en\u002Fblogs\u002F202508071.md","en\u002Fblogs\u002F202508071","openUBMC Observability: Full Insight into the System for a New BMC Vision As digital transformation surges forward, system complexities escalate continuously. The efficient monitoring and management of distributed systems have become a key challenge. As a bridge between hardware and software, the baseboard management controller (BMC) is responsible for device management, monitoring, and maintenance. openUBMC 25.06 introduces the Observability component to provide complete observability capabilities based on openTelemetry, enabling developers to clearly understand system status, quickly locate issues, and optimize system performance. This article explores the advantages, value, and prospects of openUBMC Observability. We look forward to your participation in the capability development of openUBMC Observability. Advantages 1. Unified Data Collection and Management openUBMC uses openTelemetry to implement unified collection and management of metrics, logs, and traces. All data, including hardware status, system performance, and software status, is integrated and reported to openUBMC to ensure data integrity and consistency. Standard programming APIs  \nopenUBMC encapsulates and provides application programming interfaces (APIs) based on openTelemetry to simplify data collection. Developers can easily integrate telemetry data into the BMC system through simple API calls. Standard data formats  \nThe unified telemetry framework defines compatible and consistent formats for metrics, logs, and traces, facilitating subsequent data processing and analysis. Standard transmission protocols  \nopenTelemetry Protocol (OTLP) is used, supporting both gRPC and HTTP\u002FJSON. gRPC is applicable to high-performance scenarios for efficient data transfer. HTTP\u002FJSON provides wide compatibility, facilitating integration with existing systems and tools.  2. Seamless Integration with Mainstream Tools openTelemetry Collector allows openUBMC Observability to seamlessly integrate with tools such as Prometheus, Zipkin, Jaeger, and Elasticsearch, Logstash, and Kibana (ELK). In this way, powerful data visualization and analysis capabilities are provided to help users better understand and optimize system performance. Data collection and processing \nopenTelemetry Collector supports multiple data formats and protocols, and can flexibly process telemetry data (metrics, logs, and traces) from various data sources. Data conversion and export \nopenTelemetry Collector can convert collected data and export it to different target systems, such as Prometheus, Grafana, and Jaeger. This enables the observability data from the BMC to be simultaneously used by multiple tools, thereby improving data utilization.  3. Powerful Distributed Tracing Capability With the visualized analysis capability of platforms such as Zipkin, openUBMC can clearly display the complete call paths. Developers can easily trace every operation from hardware to software, and thus quickly locate performance bottlenecks and faults.  4. High Scalability and Flexibility openUBMC provides APIs to support highly scalable observability. Developers can customize data collection and processing logic as required to meet observation requirements in different scenarios. Value Data-driven benefits: By monitoring the hardware and software status in real time, openUBMC aggregates and analyzes data to accurately identify performance bottlenecks and potential risks. With targeted data collection, it identifies and locates anomalies early in the development phase, effectively preventing failures and enhancing overall system stability and reliability. During fault locating, clear call traces and accurate performance data enable developers to quickly define the fault scope, accurately trace the root cause, and significantly shorten the fault rectification time. The following issues were identified using the observability component during the R&D of the 25.06 version: Flash log flooding  \nBy monitoring the flash write volume and analyzing its growth trend, openUBMC detected and prevented flash lifespan degradation caused by excessive writes.   Hardware access failure \nBy monitoring hardware access metrics and filtering access errors, openUBMC detected and prevented faulty hardware through the error growth trend analysis.   Improper CSR configuration  \nBy monitoring hardware access metrics and analyzing the collected data, openUBMC detected and prevented improper or invalid device access configurations in the CSR, optimizing hardware access cycles and improving overall BMC performance.   Prospects: Jointly Building openUBMC Observability openUBMC Observability is open and extensible. We welcome more developers and community partners to join us in improving and optimizing the capability. Looking ahead, we will continue focusing our efforts on the following key areas: Enhance deep integration of hardware and software.  \nDeepen the collaborative observability between hardware and software to provide a more comprehensive device management perspective. Introduce AI-driven anomaly detection.  \nUse AI technologies to intelligently analyze observed data and detect potential issues in advance. Building a developer-friendly tool chain  \nProvide more easy-to-use tools and plug-ins to lower the barrier for developers to use openUBMC Observability. Promoting community co-construction  \nWork with community developers to improve openUBMC Observability through technical sharing and open source contributions. Summary Full Insight into the System for a New BMC Vision openUBMC Observability is built based on openTelemetry. It not only improves system stability and performance, but also provides developers with an efficient and flexible platform for development and observation. We believe that through the joint efforts of the community and partners, openUBMC Observability will become more comprehensive and deliver more benefits to developers and users. If you are interested in openUBMC Observability, we warmly invite you to join our community. Let's explore and build a smarter, more reliable BMC system. Join Us to Build openUBMC Observability You are welcome to share your ideas and questions through the community forum, submit issues, or join Interface SIG regular meetings. GitCode repository:  https:\u002F\u002Fgitcode.com\u002FopenUBMC\u002Fobservability Community forum:  https:\u002F\u002Fdiscuss.openubmc.cn",[14],[789,789],null,1784971460884]