Skip to content

googleapis/google-cloud-php-logging

Folders and files

NameName
Last commit message
Last commit date

Latest commit

5cc30e0 · Jan 24, 2025
Sep 20, 2018
Feb 6, 2024
Jan 4, 2024
Jan 24, 2025
Dec 27, 2024
Jan 6, 2022
May 1, 2024
Apr 28, 2022
Feb 22, 2022
Mar 23, 2018
Dec 11, 2024
Apr 28, 2022
Jan 24, 2025
Dec 27, 2024
Feb 10, 2023
Apr 10, 2023
Apr 10, 2023
Apr 10, 2023

Stackdriver Logging for PHP

Idiomatic PHP client for Stackdriver Logging.

Latest Stable Version Packagist

NOTE: This repository is part of Google Cloud PHP. Any support requests, bug reports, or development contributions should be directed to that project.

Allows you to store, search, analyze, monitor, and alert on log data and events from Google Cloud Platform and Amazon Web Services.

Installation

To begin, install the preferred dependency manager for PHP, Composer.

Now install this component:

$ composer require google/cloud-logging

This component supports both REST over HTTP/1.1 and gRPC. In order to take advantage of the benefits offered by gRPC (such as streaming methods) please see our gRPC installation guide.

Authentication

Please see our Authentication guide for more information on authenticating your client. Once authenticated, you'll be ready to start making requests.

Sample

require 'vendor/autoload.php';

use Google\Cloud\Logging\LoggingClient;

$logging = new LoggingClient();

// Get a logger instance.
$logger = $logging->logger('my_log');

// Write a log entry.
$logger->write('my message');

// List log entries from a specific log.
$entries = $logging->entries([
    'filter' => 'logName = projects/my_project/logs/my_log'
]);

foreach ($entries as $entry) {
    echo $entry->info()['textPayload'] . "\n";
}

Debugging

Please see our Debugging guide for more information about the debugging tools.

Version

This component is considered GA (generally available). As such, it will not introduce backwards-incompatible changes in any minor or patch releases. We will address issues and requests with the highest priority.

Next Steps

  1. Understand the official documentation.
  2. Take a look at in-depth usage samples.