Download the PHP package marick/laravel-google-cloud-logging without Composer
On this page you can find all versions of the php package marick/laravel-google-cloud-logging. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-google-cloud-logging
Companion packages: Cloud Scheduler, Cloud Tasks
Introduction
This package lets you use Google Cloud Logging as the log driver for Laravel.
The package will automatically detect the environment it's running in (supports Cloud Run, App Engine, and GKE), and attach the correct labels to the log entry so the logs appear in the application service.
This package requires Laravel 12 or 13.
Installation
Install the package with Composer:
Add a new logging channel in config/logging.php:
Use the new channel:
[!IMPORTANT] A location is mandatory to make log entries appear in Cloud Run or App Engine.
How to
Use log context
Context is nested under logContext in the JSON payload, supports any structure:
Use Context
Laravel Context values are nested under laravelContext in the JSON payload:
Add labels
GCP labels are flat string key-value pairs, useful for filtering across log entries. There are three ways to add them:
Via config — applied to every log entry in the channel:
Per log entry — pass a labels key in the log context:
Per request — set once (e.g. in middleware), applied to all log entries for the request:
Configure the log name
By default, log entries are written to the laravel log. You can change this per channel:
Automatic enrichment
Every log entry is automatically enriched with the following:
HTTP request
Source location
Trace correlation
When the X-Cloud-Trace-Context header is present (injected automatically on Cloud Run and behind GCP load balancers), trace information is attached to link log entries to Cloud Trace. Requires GOOGLE_CLOUD_PROJECT (or GCLOUD_PROJECT) to be set.
Resource detection
The package detects the runtime environment and sets the correct GCP resource type so logs surface in the right place.
Cloud Run — detected via K_SERVICE and K_REVISION:
App Engine — detected via GAE_SERVICE and GAE_VERSION:
GKE — detected via KUBERNETES_SERVICE_HOST (automatically present in all pods). Set the following env vars via the Downward API to populate the resource labels:
| Env var | Resource label |
|---|---|
KUBERNETES_CLUSTER_NAME |
cluster_name |
KUBERNETES_NAMESPACE |
namespace_name |
KUBERNETES_POD_NAME |
pod_name |
KUBERNETES_CONTAINER_NAME |
container_name |
