Skip to content

DOCSP-47063: Logging #267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 13 commits into from
Jun 23, 2025
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions source/includes/monitoring-logging/logging.php
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
<?php

require 'vendor/autoload.php';

use Psr\Log\AbstractLogger;
use Psr\Log\LoggerInterface;
use Psr\Log\LogLevel;
use MongoDB\PsrLogAdapter;

use function MongoDB\add_logger;
use function MongoDB\remove_logger;

// start-register-logger
class MyLogger extends AbstractLogger
{
public array $logs = [];

public function log($level, $message, array $context = []): void
{
$this->logs[] = [$level, $message, $context['domain']];
}
}

$logger = new MyLogger();
add_logger($logger);

$uri = "mongodb://a.mongo.cosmos.azure.com:19555/";
$client = new MongoDB\Client($uri);
print_r($logger->logs);
// end-register-logger

// start-write-messages
PsrLogAdapter::writeLog(PsrLogAdapter::WARN, 'domain1', 'This is a warning message');
PsrLogAdapter::writeLog(PsrLogAdapter::CRITICAL, 'domain2', 'This is a critical message');

print_r($logger->logs);
// end-write-messages

// start-remove-logger
remove_logger($logger);
// end-remove-logger
5 changes: 4 additions & 1 deletion source/monitoring-logging.txt
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,12 @@ Monitoring and Logging

Cluster Monitoring </monitoring-logging/cluster-monitoring>
Change Streams </monitoring-logging/change-streams>
Logging </monitoring-logging/logging>

.. /monitoring/command-monitoring
.. /monitoring/connection-monitoring

- :ref:`Cluster Monitoring <php-cluster-monitoring>`: Monitor changes
in your cluster configuration
in your cluster configuration
- :ref:`Logging <php-logging>`: Configure logging to receive messages
about {+library-short+} events
195 changes: 195 additions & 0 deletions source/monitoring-logging/logging.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,195 @@
.. _php-logging:

=================
Log Driver Events
=================

.. contents:: On this page
:local:
:backlinks: none
:depth: 2
:class: singlecol

.. facet::
:name: genre
:values: reference

.. meta::
:keywords: debugging, printing

Overview
--------

In this guide, you can learn how to use the {+library-short+} to
set up and configure **logging**. Logging allows you to receive
information about database operations, server connections, errors,
and other events that occur while your application runs.

The {+library-short+} supports `Psr\\Log\\LoggerInterface
<https://www.php-fig.org/psr/psr-3/#3-psrlogloggerinterface>`__, a PSR-3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

S: consider linking to the general page instead of an anchor

logger interface that configures your application to receive log messages.
You can register one or more ``Psr\Log\LoggerInterface`` objects to
send messages to the logger. The {+library-short+} is built on top of
``libmongoc`` and the {+extension-short+}, so the logger receives event notifications
from both components.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see 3 components in this list: the C driver, the PHP extension, the PHP library.


Register a Logger
-----------------

To configure your application to receive messages about driver events,
create a logger class that implements the ``Psr\Log\LoggerInterface``
interface. Then, use the ``MongoDB\add_logger()`` function to register
your logger.

Each log message includes the following information:

- Log level: Indicates the severity of the message. To view a list of
possible levels, see `PSR\\Log\\LogLevel <https://www.php-fig.org/psr/psr-3/#5-psrlogloglevel>`__.
- Message: Describes the logged event.
- Domain string: Specifies the driver component that emitted the log message.

To implement ``Psr\Log\LoggerInterface``, you can create a class that
extends the ``Psr\Log\AbstractLogger`` class. ``AbstractLogger`` implements
``LoggerInterface`` and a generic ``log()`` method, which receives log
messages at each severity level.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We recommend using a psr/log-implementation


Example
~~~~~~~

This example performs the following actions:

- Creates a logger called ``MyLogger`` that extends the ``AbstractLogger`` class
and records the log level, description, and domain of each event
- Registers the logger
- Creates a client that connects to a CosmosDB cluster
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

S: I'm guessing that you are connecting to this cluster because it will generate an info message, but perhaps you should ping Rishabh to ask if we want to demonstrate this as an example

- Prints each log message

.. io-code-block::
:copyable:

.. input:: /includes/monitoring-logging/logging.php
:start-after: start-register-logger
:end-before: end-register-logger
:language: php
:dedent:

.. output::
:visible: false

Array
(
[0] => Array
(
[0] => debug
[1] => Connection string: 'mongodb://a.mongo.cosmos.azure.com:19555/'
[2] => PHONGO
)
[1] => Array
(
[0] => debug
[1] => Creating Manager, phongo-1.21.0[stable] - mongoc-1.30.1(bundled), libbson-1.30.1(bundled), php-8.4.4
[2] => PHONGO
)
[2] => Array
(
[0] => debug
[1] => Setting driver handshake data: { name: 'ext-mongodb:PHP / PHPLIB ', version: '1.21.0 / 1.21.1 ', platform: 'PHP 8.4.4 ' }
[2] => PHONGO
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q: What is PHONGO? might be worth describing what types of things users might expect to see here

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It means the log entry comes from the PHP extension. I will ask dbx if PHONGO (the extension) and mongoc (the c driver) are the only possible domains and I'll add that information

)
[3] => Array
(
[0] => info
[1] => You appear to be connected to a CosmosDB cluster. For more information regarding feature compatibility and support please visit https://www.mongodb.com/supportability/cosmosdb
[2] => mongoc
)
[4] => Array
(
[0] => debug
[1] => Created client with hash: a:4:{s:3:"pid";i:61731;s:3:"uri";s:41:"mongodb://a.mongo.cosmos.azure.com:19555/";s:7:"options";a:0:{}s:13:"driverOptions";a:1:{s:6:"driver";a:2:{s:4:"name";s:6:"PHPLIB";s:7:"version";s:6:"1.21.1";}}}
[2] => PHONGO
)
[5] => Array
(
[0] => debug
[1] => Stored persistent client with hash: a:4:{s:3:"pid";i:61731;s:3:"uri";s:41:"mongodb://a.mongo.cosmos.azure.com:19555/";s:7:"options";a:0:{}s:13:"driverOptions";a:1:{s:6:"driver";a:2:{s:4:"name";s:6:"PHPLIB";s:7:"version";s:6:"1.21.1";}}}
[2] => PHONGO
)
)

The preceding output includes log messages with a ``debug`` severity level, which
describe normal driver activities. It also includes a message about the CosmosDB

Check failure on line 120 in source/monitoring-logging/logging.txt

View workflow job for this annotation

GitHub Actions / TDBX Vale rules

[vale] reported by reviewdog 🐶 [MongoDB.Accessibility] Don't use language (such as 'normal') that defines people by their disability. Raw Output: {"message": "[MongoDB.Accessibility] Don't use language (such as 'normal') that defines people by their disability.", "location": {"path": "source/monitoring-logging/logging.txt", "range": {"start": {"line": 120, "column": 10}}}, "severity": "ERROR"}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

S: to resolve the vale issue you could use a phrase like "These messages provide updates on the state of the connection" as normal is subjective

connection with an ``info`` level that describes a noteworthy but non-urgent
event.

Write Custom Log Messages
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no point in writing to the MongoDB adapter from the application. The application will write to the psr logger directly and get a better interoperability.

This is noted in the comment of the method: https://github.com/mongodb/mongo-php-library/blob/19722556e2a9ecd62fcd341b868dde9b8fae6ec6/src/PsrLogAdapter.php#L128

This function is intended for internal use within the library.

-------------------------

You can generate custom log messages by using the ``PsrLogAdapter::writeLog()``
function. This function allows you to write directly to the logger and
can help with application monitoring and debugging. Pass the severity level, domain, and
description as parameters to ``writeLog()``.

The following example writes log messages that have ``warning`` and
``critical`` severity levels to the logger:

.. io-code-block::
:copyable:

.. input:: /includes/monitoring-logging/logging.php
:start-after: start-write-messages
:end-before: end-write-messages
:language: php
:dedent:

.. output::
:visible: false

Array
(
[0] => Array
(
[0] => warning
[1] => This is a warning message
[2] => domain1
)
[1] => Array
(
[0] => critical
[1] => This is a critical message
[2] => domain2
)
)

Remove a Logger
---------------

To unregister a logger, pass your logger object as a parameter to the ``MongoDB\remove_logger()``
function. After calling this function, your logger no longer receives log
messages about your application.

The following example unregisters a logger:

.. literalinclude:: /includes/monitoring-logging/logging.php
:language: php
:start-after: start-remove-logger
:end-before: end-remove-logger
:dedent:

Additional Information
----------------------

To learn more about the PSR-3 logger, see `PSR-3: Logger Interface
<https://www.php-fig.org/psr/psr-3/>`__ in the PHP-FIG documentation.

API Documentation
~~~~~~~~~~~~~~~~~

To learn more about the {+library-short+} methods discussed in this guide, see the
following API documentation:

- :phpmethod:`MongoDB\add_logger()`
- :phpmethod:`MongoDB\remove_logger()`

To learn more about C driver logging behavior, see `Logging
<https://mongoc.org/libmongoc/current/logging.html>`__ in the ``libmongoc``
API documentation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To learn more about C driver logging behavior, see `Logging
<https://mongoc.org/libmongoc/current/logging.html>`__ in the ``libmongoc``
API documentation.
To learn more about how the underlying C driver generates log messages, see `Logging
<https://mongoc.org/libmongoc/current/logging.html>`__ in the ``libmongoc``
API documentation.

Loading