Jika Anda berhasil mengirim permintaan ke API, tetapi tidak melihat metrik atau log di halaman Endpoints > Services di konsolGoogle Cloud , lakukan langkah-langkah berikut:
Jika Anda perlu mengakses log Extensible Service Proxy (ESP) untuk mendiagnosis masalah, gunakan kubectl sebagai berikut:
Dapatkan nama pod:
kubectl get pod
NAME READY STATUS RESTARTS AGE
esp-echo-174578890-x09gl 2/2 Running 2 21s
Nama pod adalah esp-echo-174578890-x09gl dan memiliki dua penampung: esp
dan echo.
Untuk melihat log di pod, gunakan kubectl logs:
kubectl logs POD_NAME -c CONTAINER_NAME
Dengan POD_NAME dan
CONTAINER_NAME ditampilkan dari
perintah
kubectl get pod, di langkah sebelumnya. Contoh:
kubectl logs esp-echo-174578890-x09gl -c esp
Memverifikasi nama layanan
Jika Anda melihat pesan error Fetching service config failed, pastikan
nama layanan yang Anda tentukan di kolom --service dalam file manifes Deployment (disebut sebagai file deployment.yaml) cocok dengan nama di
kolom host dalam dokumen OpenAPI Anda (disebut sebagai file openapi.yaml).
Jika nama yang salah ada dalam file deployment.yaml:
Buka file deployment.yaml dan buka bagian yang dikonfigurasi untuk penampung ESP. Contoh:
Ganti SERVICE_NAME dengan nama dari langkah sebelumnya. Perlu waktu 30 hari agar layanan dihapus dari
Google Cloud. Anda tidak dapat menggunakan kembali nama layanan selama waktu ini.
Buka file openapi.yaml dan perbaiki nama di kolom host, lalu simpan
file.
Deploy konfigurasi layanan yang telah diperbarui:
gcloud endpoints services deploy openapi.yaml
Tunggu hingga konfigurasi layanan berhasil di-deploy.
Mulai layanan Kubernetes:
kubectl create -f deployment.yaml
Memeriksa file konfigurasi
Gunakan ssh untuk terhubung ke pod menggunakan kubectl:
kubectl exec -ti -c CONTAINER_NAMEPOD_NAME bash
Ganti CONTAINER_NAME dengan nama
penampung dan POD_NAME dengan nama pod Anda.
Di direktori etc/nginx/endpoints/, periksa file konfigurasi berikut untuk menemukan error:
nginx.conf- File konfigurasi nginx dengan perintah ESP
service.jso - File konfigurasi layanan
Mengakses halaman status Endpoints
Jika Anda menetapkan rollout_strategy ke managed saat memulai ESP,
dan Anda perlu mengetahui ID konfigurasi yang digunakan instance
ESP, halaman status Endpoint memiliki informasi tersebut.
Untuk mengakses halaman status Endpoints:
Gunakan ssh untuk terhubung ke pod menggunakan kubectl:
kubectl exec -ti -c CONTAINER_NAMEPOD_NAME bash
Ganti CONTAINER_NAME dengan nama
penampung dan POD_NAME dengan nama pod Anda.
Nilai di rolloutId adalah ID konfigurasi layanan yang
digunakan ESP. Untuk memastikan ESP menggunakan konfigurasi yang sama dengan Endpoint, lihat Mendapatkan nama layanan dan ID konfigurasi.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis document provides troubleshooting steps for issues encountered when deploying Endpoints on Google Kubernetes Engine (GKE) and Kubernetes.\u003c/p\u003e\n"],["\u003cp\u003eIf the error \u003ccode\u003eFailed in kubectl create -f gke.yaml\u003c/code\u003e occurs, you will need to authorize \u003ccode\u003egcloud\u003c/code\u003e, create a cluster, and make cluster credentials available to \u003ccode\u003ekubectl\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo resolve missing metrics or logs in the Google Cloud console, verify that all required services are enabled and that all required permissions are granted.\u003c/p\u003e\n"],["\u003cp\u003eTo check if the service name is correct, ensure that the \u003ccode\u003e--service\u003c/code\u003e field in your \u003ccode\u003edeployment.yaml\u003c/code\u003e file matches the \u003ccode\u003ehost\u003c/code\u003e field in your \u003ccode\u003eopenapi.yaml\u003c/code\u003e file, correcting either one if they are mismatched.\u003c/p\u003e\n"],["\u003cp\u003eTo diagnose issues with the Extensible Service Proxy (ESP), you can view the logs using \u003ccode\u003ekubectl logs\u003c/code\u003e, check configuration files in the \u003ccode\u003eetc/nginx/endpoints/\u003c/code\u003e directory, or access the Endpoints status page for configuration ID details.\u003c/p\u003e\n"]]],[],null,["# Troubleshooting Cloud Endpoints in GKE\n\nOpenAPI \\| [gRPC](/endpoints/docs/grpc/troubleshoot-gke-deployment \"View this page for the Cloud Endpoints gRPC docs\")\n\n\u003cbr /\u003e\n\nThis document presents troubleshooting techniques for Endpoints\ndeployments on Google Kubernetes Engine (GKE) and Kubernetes.\n\nFailed in `kubectl create -f gke.yaml`\n--------------------------------------\n\nIf you see the `Failed in kubectl create -f gke.yaml` error message, take the\nfollowing steps:\n\n1. Authorize `gcloud`:\n\n gcloud auth login\n gcloud auth application-default login\n\n2. Create a cluster. You can either use the following `gcloud`command, or create\n a cluster using\n [Google Cloud console](https://console.cloud.google.com/kubernetes).\n\n ```\n gcloud container clusters create CLUSTER_NAME\n ```\n\n Replace \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e with your cluster's name.\n3. Get credentials for your cluster and make them available to `kubectl`:\n\n ```\n gcloud container clusters get-credentials CLUSTER_NAME\n ```\n\nEndpoints metrics and logs aren't displayed\n-------------------------------------------\n\nIf you can successfully send requests to your API, but you don't see any\nmetrics or logs on the **Endpoints** \\\u003e **Services** page in the\nGoogle Cloud console, take the following steps:\n\n1. Check all the [required services](/endpoints/docs/openapi/get-started-kubernetes-engine#checking_required_services) are enabled.\n2. Check all the [required permissions](/endpoints/docs/openapi/get-started-kubernetes-engine#checking_required_permissions) are granted.\n\nAccessing logs from Extensible Service Proxy\n--------------------------------------------\n\nIf you need to access the Extensible Service Proxy (ESP) logs to diagnose\nproblems, use `kubectl` as follows:\n\n1. Get the name of the pod:\n\n kubectl get pod\n\n NAME READY STATUS RESTARTS AGE\n esp-echo-174578890-x09gl 2/2 Running 2 21s\n\n The pod name is `esp-echo-174578890-x09gl` and it has two containers: `esp`\n and `echo`.\n2. To view the logs in a pod use `kubectl logs`:\n\n ```\n kubectl logs POD_NAME -c CONTAINER_NAME\n ```\n\n Where `POD_NAME` and\n `CONTAINER_NAME` are returned from the\n `kubectl get pod`\n command, in the previous step. For example: \n\n kubectl logs esp-echo-174578890-x09gl -c esp\n\nVerifying the service name\n--------------------------\n\nIf you see the error message `Fetching service config failed`, verify that the service name that you specified in the `--service` field in your Deployment manifest file (referred to as the `deployment.yaml` file) matches the name in the `host` field in your OpenAPI document (referred to as the `openapi.yaml` file).\n\n\u003cbr /\u003e\n\n**If the incorrect name is in the `deployment.yaml` file**:\n\n1. Open the `deployment.yaml` file and go to the section configured for the\n ESP container. For example:\n\n ```\n containers:\n - name: esp\n image: gcr.io/endpoints-release/endpoints-runtime:1\n args: [\n \"--http_port=8081\",\n \"--backend=127.0.0.1:8080\",\n \"--service=SERVICE_NAME\",\n \"--rollout_strategy=managed\"\n ]\n ```\n\n Change \u003cvar translate=\"no\"\u003eSERVICE_NAME\u003c/var\u003e so that it matches the name in\n the `host` field in the `openapi.yaml` and save the `deployment.yaml` file.\n2. Start the Kubernetes service:\n\n kubectl create -f deployment.yaml\n\n**If the incorrect name is in the `openapi.yaml` file**:\n\n1. [Get the service name](/endpoints/docs/openapi/get-service-name-config-id)\n that Endpoints was configured to use.\n\n2. Delete the service:\n\n ```\n gcloud endpoints services delete SERVICE_NAME\n ```\n\n Replace \u003cvar translate=\"no\"\u003eSERVICE_NAME\u003c/var\u003e with the name from the\n previous step. It takes 30 days for the service to be deleted from\n Google Cloud. You aren't able to reuse the service name during this time.\n3. Open the `openapi.yaml` file and correct the name in the `host` field and save\n the file.\n\n4. Deploy the updated service configuration:\n\n gcloud endpoints services deploy openapi.yaml\n\n5. Wait for the service configuration to be successfully deployed.\n\n6. Start the Kubernetes service:\n\n kubectl create -f deployment.yaml\n\nChecking configuration files\n----------------------------\n\n1. Use `ssh` to connect to the pod using `kubectl`:\n\n ```\n kubectl exec -ti -c CONTAINER_NAME POD_NAME bash\n ```\n\n Replace \u003cvar translate=\"no\"\u003eCONTAINER_NAME\u003c/var\u003e with the name of your\n container and \u003cvar translate=\"no\"\u003ePOD_NAME\u003c/var\u003e with the name of your pod.\n2. In the `etc/nginx/endpoints/` directory, check the following configuration\n files for errors:\n\n - `nginx.conf`- The `nginx` config file with ESP directives\n - `service.jso` - The service configuration file\n\nAccessing the Endpoints status page\n-----------------------------------\n\nIf you set `rollout_strategy` to `managed` when you started ESP,\nand you need to find out the configuration ID that an instance of\nESP is using, the Endpoints status page has the information.\n\nTo access the Endpoints status page:\n\n1. Use `ssh` to connect to the pod using `kubectl`:\n\n ```\n kubectl exec -ti -c CONTAINER_NAME POD_NAME bash\n ```\n\n Replace \u003cvar translate=\"no\"\u003eCONTAINER_NAME\u003c/var\u003e with the name of your\n container and \u003cvar translate=\"no\"\u003ePOD_NAME\u003c/var\u003e with the name of your pod.\n2. Install [`curl`](https://curl.haxx.se/download.html).\n\n3. Enter the following:\n\n curl http://localhost:8090/endpoints_status\n\n It displays something similar the following: \n\n \"serviceConfigRollouts\": {\n \"rolloutId\": \"2017-08-09r27\",\n \"percentages\": {\n \"2017-08-09r26\": \"100\"\n }\n }\n\nThe value in the `rolloutId` is the service configuration ID that\nESP is using. To make sure that ESP is using the\nsame configuration as Endpoints,\nsee\n[Getting the service name and configuration ID](/endpoints/docs/openapi/get-service-name-config-id)."]]
