Sign in to your Google Cloud account. If you're new to
Google Cloud,
create an account to evaluate how our products perform in
real-world scenarios. New customers also get $300 in free credits to
run, test, and deploy workloads.
In the Google Cloud console, on the project selector page,
select or create a Google Cloud project.
[[["わかりやすい","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-07-30 UTC。"],[],[],null,["# Setting Up Cloud Logging for PHP\n\nYou can write logs to Cloud Logging from PHP applications by\nusing the Cloud Logging library for PHP directly.\n\n\u003cbr /\u003e\n\nBefore you begin\n----------------\n\n- Sign in to your Google Cloud account. If you're new to Google Cloud, [create an account](https://console.cloud.google.com/freetrial) to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n-\n\n\n Enable the Cloud Logging API.\n\n\n [Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=logging.googleapis.com)\n\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n-\n\n\n Enable the Cloud Logging API.\n\n\n [Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=logging.googleapis.com)\n\n\nInstalling the Cloud Logging library for PHP\n--------------------------------------------\n\nThe Cloud Logging library for PHP provides a simple [PSR-3](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-3-logger-interface.md)\nlogger implementation for PHP web frameworks.\n\nTo write logs from your app, add the Cloud Logging library for PHP to your composer.json: \n\n composer require google/cloud-logging\n\n### Creating a PSR-3 logger\n\nUse the following code to create a PSR-3 logger: \n\n use Google\\Cloud\\Logging\\LoggingClient;\n\n $logging = new LoggingClient([\n 'projectId' =\u003e $projectId\n ]);\n $logger = $logging-\u003epsrLogger('app');\n\n### Enabling batching option\n\n| **Note:** This step is optional.\n\nThe PSR-3 logger sends the logs synchronously. This means that\nwhenever you emit a log, it will add RPC latency to the user\nrequest. Especially if you emit multiple logs in a single request, the\nadded latency will be significant. You probably want to avoid that.\n\nThe following code creates a PSR-3 logger which will batch multiple\nlogs into one single RPC calls: \n\n $logger = LoggingClient::psrBatchLogger('app');\n\nBy default, this logger batches the logs within a single process. On\nApp Engine flexible environment, you can configure the Cloud Logging library for PHP for\neven higher throughput and lower latency. For details, see\n[Configuring the logging daemon](#gae-config).\n\n### Configuring the Cloud Logging library for PHP\n\nYou can customize the behavior of the Cloud Logging library for PHP. See\n[the configuration document](/php/docs/reference/cloud-logging/latest/LoggingClient#_Google_Cloud_Logging_LoggingClient____construct__)\nfor a list of possible configuration options.\n\nUsing the PSR-3 logger\n----------------------\n\nOnce the logger is created, you can use the logger in your\napplication: \n\n $logger-\u003einfo('Hello World');\n $logger-\u003eerror('Oh no');\n\n\u003cbr /\u003e\n\nFor more information on installation, see the\n[documentation](https://github.com/googleapis/google-cloud-php/tree/master/Logging) for the\nCloud Logging library for PHP. You can also report issues using the\n[issue tracker](https://github.com/googleapis/google-cloud-php/issues).\n\nWrite logs with the Cloud Logging client library\n------------------------------------------------\n\nFor information on using the Cloud Logging client library for\nPHP directly, see [Cloud Logging Client Libraries](/logging/docs/reference/libraries).\n\nRun on Google Cloud\n-------------------\n\nFor an application to write logs by using the Cloud Logging library for PHP, the\nservice account for the underlying resource must have the\n[Logs Writer (`roles/logging.logWriter`)](/logging/docs/access-control#permissions_and_roles) [IAM](/iam/docs/understanding-roles) role.\nMost Google Cloud environments automatically configure the default\nservice account to have this role.\n\n### App Engine\n\nCloud Logging is automatically enabled for App Engine, and your app's\n[default service account](/appengine/docs/standard/php7/service-account) has\nthe IAM permissions by default to write log entries.\n\nFor more information, see [Writing and viewing\nlogs](/appengine/docs/standard/php7/writing-application-logs).\n\n\nHowever, we recommend that you use the PSR-3 logger which automatically\nadds metadata to your logs so that your application logs are\ncorrelated to the request logs.\n\n#### Configuring the daemon for App Engine flexible environment\n\nIn the App Engine flexible environment, you can configure the\nCloud Logging library for PHP to use an external daemon program to maximize the\nlog throughput and minimize the app's latency. To enable this feature,\nadd the following line to `runtime_config` section in `app.yaml`: \n\n enable_stackdriver_integration: true\n\n### Google Kubernetes Engine (GKE)\n\n[GKE](/kubernetes-engine/docs) automatically grants the default service account\nthe [Logs Writer (`roles/logging.logWriter`)](/logging/docs/access-control#permissions_and_roles) IAM role.\nIf you use\n[Workload Identity Federation for GKE](/kubernetes-engine/docs/concepts/workload-identity)\nwith this default service account to let workloads access specific\nGoogle Cloud APIs, then no additional configuration is required.\nHowever, if you use Workload Identity Federation for GKE with a\ncustom IAM service account, then ensure that the custom service\naccount has the role of Logs Writer (`roles/logging.logWriter`).\n\nIf needed, you can also use the following command to add the `logging.write`\naccess scope when creating the cluster: \n\n gcloud container clusters create example-cluster-name \\\n --scopes https://www.googleapis.com/auth/logging.write\n\n### Compute Engine\n\n| **Note:** To use the Cloud Logging library for PHP on a **Compute Engine** VM instance, you do not need to install the Cloud Logging agent.\n\nWhen using [Compute Engine](/compute/docs) VM instances, add the `cloud-platform`\naccess scope to each instance. When creating a new instance through the\nGoogle Cloud console, you can do this in the **Identity and API access** section\nof the **Create Instance** panel. Use the Compute Engine default service\naccount or another service account of your choice, and select\n**Allow full access to all Cloud APIs** in the **Identity and API access**\nsection. Whichever service\naccount you select, ensure that it has been granted the\n[Logs Writer role](/logging/docs/access-control#permissions_and_roles) in the **IAM \\& Admin** section of the\nGoogle Cloud console.\n\nRun locally and elsewhere\n-------------------------\n\nTo use the Cloud Logging library for PHP outside of Google Cloud,\nincluding running the library on your own workstation, on your data center's\ncomputers, or on the VM instances of another cloud provider, you must\nset up Application Default Credentials (ADC) in your local environment to\nauthenticate to the Cloud Logging library for PHP.\n\nFor more information, see\n[Set up ADC for on-premises or another cloud provider](/docs/authentication/set-up-adc-on-premises).\n\nView the logs\n-------------\n\nIn the Google Cloud console, go to the **Logs Explorer** page:\n\n[Go to **Logs Explorer**](https://console.cloud.google.com/logs/query)\n\n\u003cbr /\u003e\n\nIf you use the search bar to find this page, then select the result whose subheading is\n**Logging**.\n\nIn the Logs Explorer, you must specify one or more resources, but the resource\nselection might not be obvious. Here are some tips to help you get\nstarted:\n\n- If you are deploying your application to App Engine or using the\n App Engine-specific libraries, set your resource to\n **GAE Application**.\n\n- If you are deploying your application on Compute Engine, set the resource\n to **GCE VM Instance**.\n\n- If you are deploying your application on Google Kubernetes Engine, your\n cluster's logging configuration determines the resource type of the log\n entries. For a detailed\n discussion on the Legacy Google Cloud Observability and the Google Cloud Observability\n Kubernetes Monitoring solutions, and how those options affect the\n resource type, see\n [Migrating to Google Cloud Observability Kubernetes Monitoring](/monitoring/kubernetes-engine/migration#stackdriver-options).\n\n- If your application is using the Cloud Logging API directly,\n the resource is dependent on the API and your configuration. For example,\n in your application, you can specify a resource or use a default resource.\n\n- If you don't see any logs in the Logs Explorer, to see all log entries,\n switch to the advanced query mode and use an empty query.\n\n 1. To switch to the advanced query mode, click **menu** (▾) at the top of the Logs Explorer and then select **Convert to advanced filter**.\n 2. Clear the content that appears in the filter box.\n 3. Click **Submit Filter**.\n\n You can examine the individual entries to identify your resources.\n\nFor additional information, see [Using the Logs Explorer](/logging/docs/view/logs-explorer-interface)."]]
