자동 문제 표시(AIS)는 Hybrid 클러스터 내에서 감지된 진행 중인 문제에 대한 빠른 정보를 제공합니다. 이 정보에는 문제 해결 및 해결 방법 문서 링크가 포함됩니다. 자동 문제 표시는 시스템에서 감지 가능한 알려진 일반적인 문제만 찾으며 클러스터 내의 모든 문제를 감지할 수는 없습니다.
Apigee Hybrid v1.10부터 Apigee 런타임 감시자 구성요소가 컨트롤 플레인 및 Kubernetes API 서버 상태를 자동으로 스캔하여 구성 문제가 있는지 확인합니다.
기본적으로 스캔은 60초마다 수행됩니다. 원하는 경우 간격을 변경하거나 스캔을 중지할 수 있습니다.
AIS가 문제를 감지하면 Kubernetes API 서버 내에 새 ApigeeIssue 인스턴스를 만듭니다. 이러한 인스턴스에는 문제에 관한 정보와 특정 문제에 관한 문서 링크가 포함되어 있습니다.
문제가 해결되어 스캔에서 이 문제가 더 이상 발생하지 않는 것으로 확인되면 Kubernetes API 서버에서 자동으로 삭제됩니다.
자동 문제 표시 사용
kubectl get apigeeissues 명령어로 기존 문제가 있는지 확인합니다.
kubectl -n APIGEE_NAMESPACE get apigeeissues
예를 들면 다음과 같습니다.
kubectl -n APIGEE_NAMESPACE get apigeeissues
NAME SEVERITY AGE URL
vhost-missing-eg-nonprod Error 1hr https://cloud.google.com/apigee/docs/hybrid/MISSING_ENV_GROUP
control-plane-connectivity-failure Error 1d https://cloud.google.com/apigee/docs/hybrid/OLD_TLS_VERSION
특정 문제에 대한 자세한 내용을 보려면 문제 이름과 함께 kubectl describe 명령어를 사용하세요. 이름 앞에 apigeeissues/를 붙여야 합니다(예: apigeeissues vhost-missing-eg-nonprod).
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eAutomated Issue Surfacing (AIS) quickly identifies known issues within your Hybrid cluster and provides links to relevant documentation for troubleshooting.\u003c/p\u003e\n"],["\u003cp\u003eStarting with Apigee hybrid v1.10, the runtime watcher automatically scans the control plane and Kubernetes API server every 60 seconds to detect configuration issues, which can be adjusted in your configuration.\u003c/p\u003e\n"],["\u003cp\u003eWhen AIS detects an issue, it generates an \u003ccode\u003eApigeeIssue\u003c/code\u003e instance within the Kubernetes API server, and you can use \u003ccode\u003ekubectl get apigeeissues\u003c/code\u003e to view detected issues.\u003c/p\u003e\n"],["\u003cp\u003eIssues are automatically deleted from the Kubernetes API server once they are resolved, as detected by the continuous scanning process.\u003c/p\u003e\n"],["\u003cp\u003eYou can disable the automated issue surfacing entirely, by using \u003ccode\u003ewatcher.args.enableIssueScanning: false\u003c/code\u003e property in the overrides file, if desired.\u003c/p\u003e\n"]]],[],null,["# Automated issue surfacing\n\n| You are currently viewing version 1.13 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\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.13/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.13/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."]]
