[[["易于理解","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-08-27。"],[],[],null,["# Automated issue surfacing\n\nOverview\n--------\n\n\nAutomated issue surfacing (AIS) provides quick information about ongoing issues detected within\nyour Hybrid cluster. This information includes links to documentation for troubleshooting and\nresolution. Automated issue surfacing only looks for known, common, system detectable issues and\ncannot detect all the issues within a cluster.\n\nStarting with Apigee hybrid v1.10, the Apigee runtime watcher component automatically scans the\ncontrol plane and Kubernetes API server state to determine if there are any configuration issues.\nBy default, the scanning happens every 60 seconds. You can change the interval or disable\nscanning if you prefer.\n\nWhen AIS detects an issue, it creates a new instance of `ApigeeIssue` within\nthe Kubernetes API server. These instances contain information about the issues and links to\ndocumentation on the specific issues.\n\nWhen you resolve issues, they will automatically be deleted from the Kubernetes API server when\nthe scanning determines they are no longer occurring.\n\nUsing Automated issue surfacing.\n--------------------------------\n\nCheck for any existing issues with the `kubectl get apigeeissues` command: \n\n```\nkubectl -n APIGEE_NAMESPACE get apigeeissues\n```\n\nFor example: \n\n```\nkubectl -n APIGEE_NAMESPACE get apigeeissues\n\nNAME SEVERITY AGE URL\nvhost-missing-eg-nonprod Error 1hr https://cloud.google.com/apigee/docs/hybrid/MISSING_ENV_GROUP\ncontrol-plane-connectivity-failure Error 1d https://cloud.google.com/apigee/docs/hybrid/OLD_TLS_VERSION\n```\n\nFor more detailed information about a specific issue, use the `kubectl describe`\ncommand with the issue name. The name must be preceded by `apigeeissues/` for example:\n`apigeeissues `**vhost-missing-eg-nonprod**. \n\n```\nkubectl -n APIGEE_NAMESPACE describe apigeeissues vhost-missing-eg-nonprod\n\nName: vhost-missing-eg-nonprod\nNamespace: apigee\nLabels: \nAnnotations: \nAPI Version: apigee.cloud.google.com/v1alpha1\nKind: ApigeeIssue\nMetadata:\n Creation Timestamp: 2022-08-25T20:41:56Z\n Managed Fields:\n API Version: apigee.cloud.google.com/v3\n Resource Version: 12345678\n UID: aaaaaaaa-bbbb-cccc-dddd-eeeeffffgggg\nSpec:\n Severity: Error\n Reason: MISSING_ENV_GROUP\n Details: Expected envgroup \"nonprod\" for ApigeeRouteConfig \"my-org-nonprod\"\n Documentation: https://cloud.google.com/apigee/docs/hybrid/MISSING_ENV_GROUP\n Ignore: false\n IgnoreReason:\nEvents: \n```\n\nChanging the scan interval\n--------------------------\n\nBy default, Watcher scans the control plane for issues once every 60 seconds. To change the\nscan interval, specify the new interval in seconds with the\n[`watcher.args.issueScanInterval`](/apigee/docs/hybrid/v1.15/config-prop-ref#watcher-args-issuescaninterval)\nproperty in your overrides file. For example: \n\n```\nwatcher:\n args:\n issueScanInterval: 120\n```\n\n\nApply the configuration.\n\nUpgrade the `apigee-env` chart for each Apigee environment. \n\n```\nhelm upgrade $ORG_NAME apigee-org/ \\\n --namespace APIGEE_NAMESPACE \\\n -f OVERRIDES_FILE \n```\n\nDisabling automated issue surfacing\n-----------------------------------\n\nYou can disable Automated issue surfacing by setting the\n[`watcher.args.enableIssueScanning`](/apigee/docs/hybrid/v1.15/config-prop-ref#watcher-args-enableissuescanning)\nproperty to `false` in your overrides file. For example: \n\n```\nwatcher:\n args:\n enableIssueScanning: false\n```\n\n\nApply the configuration.\n\nUpgrade the `apigee-env` chart for each Apigee environment. \n\n```\nhelm upgrade $ORG_NAME apigee-org/ \\\n --namespace APIGEE_NAMESPACE \\\n -f OVERRIDES_FILE \n```\n\nRelated troubleshooting guides\n------------------------------\n\nAutomated issue surfacing can provide links directly to the troubleshooting guides, including:\n\n- [No network\n connectivity between runtime plane and control plane](/apigee/docs/api-platform/troubleshoot/playbooks/no-network-connectivity)\n- [Virtual host\n missing environment group](/apigee/docs/api-platform/troubleshoot/playbooks/vh-missing-env-group)\n- [Ingress\n cert mismatch](/apigee/docs/api-platform/troubleshoot/playbooks/ingress-cert-mismatch)\n\nSee [Introduction to Apigee X\nand Apigee hybrid playbooks](/apigee/docs/api-platform/troubleshoot/playbooks/introduction) for an overview and list of Apigee troubleshooting guides."]]