[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-07-02。"],[[["This content focuses on how to investigate Operations Anomalies within the Apigee UI in Cloud console, contrasting it with the Anomaly Detection in the classic Apigee UI."],["Anomalies detected in the Operations Anomalies dashboard can be further examined using the API Monitoring dashboards to access specific API data related to the anomaly's timeframe."],["The API Monitoring Investigate dashboard, accessible by clicking \"Investigate\" on an anomaly, displays an error rate timeline, and a breakdown of errors by fault codes, helping pinpoint the anomaly's origin."],["By examining the Fault Code by Time graph, users can identify the specific fault code triggering the anomaly, as demonstrated with the `steps.json2xml.SourceUnavailable` example."],["Users can further investigate by drilling down into fault code data or creating alerts for similar anomalies to receive notifications about future occurrences."]]],[]]