monitoring – Tools for monitoring driver events.

Tools to monitor driver events.

New in version 3.1.

Attention

Starting in PyMongo 3.11, the monitoring classes outlined below are included in the PyMongo distribution under the event_loggers submodule.

Use register() to register global listeners for specific events. Listeners must inherit from one of the abstract classes below and implement the correct functions for that class.

For example, a simple command logger might be implemented like this:

  1. import logging
  2. from pymongo import monitoring
  3. class CommandLogger(monitoring.CommandListener):
  4. def started(self, event):
  5. logging.info("Command {0.command_name} with request id "
  6. "{0.request_id} started on server "
  7. "{0.connection_id}".format(event))
  8. def succeeded(self, event):
  9. logging.info("Command {0.command_name} with request id "
  10. "{0.request_id} on server {0.connection_id} "
  11. "succeeded in {0.duration_micros} "
  12. "microseconds".format(event))
  13. def failed(self, event):
  14. logging.info("Command {0.command_name} with request id "
  15. "{0.request_id} on server {0.connection_id} "
  16. "failed in {0.duration_micros} "
  17. "microseconds".format(event))
  18. monitoring.register(CommandLogger())

Server discovery and monitoring events are also available. For example:

  1. class ServerLogger(monitoring.ServerListener):
  2. def opened(self, event):
  3. logging.info("Server {0.server_address} added to topology "
  4. "{0.topology_id}".format(event))
  5. def description_changed(self, event):
  6. previous_server_type = event.previous_description.server_type
  7. new_server_type = event.new_description.server_type
  8. if new_server_type != previous_server_type:
  9. # server_type_name was added in PyMongo 3.4
  10. logging.info(
  11. "Server {0.server_address} changed type from "
  12. "{0.previous_description.server_type_name} to "
  13. "{0.new_description.server_type_name}".format(event))
  14. def closed(self, event):
  15. logging.warning("Server {0.server_address} removed from topology "
  16. "{0.topology_id}".format(event))
  17. class HeartbeatLogger(monitoring.ServerHeartbeatListener):
  18. def started(self, event):
  19. logging.info("Heartbeat sent to server "
  20. "{0.connection_id}".format(event))
  21. def succeeded(self, event):
  22. # The reply.document attribute was added in PyMongo 3.4.
  23. logging.info("Heartbeat to server {0.connection_id} "
  24. "succeeded with reply "
  25. "{0.reply.document}".format(event))
  26. def failed(self, event):
  27. logging.warning("Heartbeat to server {0.connection_id} "
  28. "failed with error {0.reply}".format(event))
  29. class TopologyLogger(monitoring.TopologyListener):
  30. def opened(self, event):
  31. logging.info("Topology with id {0.topology_id} "
  32. "opened".format(event))
  33. def description_changed(self, event):
  34. logging.info("Topology description updated for "
  35. "topology id {0.topology_id}".format(event))
  36. previous_topology_type = event.previous_description.topology_type
  37. new_topology_type = event.new_description.topology_type
  38. if new_topology_type != previous_topology_type:
  39. # topology_type_name was added in PyMongo 3.4
  40. logging.info(
  41. "Topology {0.topology_id} changed type from "
  42. "{0.previous_description.topology_type_name} to "
  43. "{0.new_description.topology_type_name}".format(event))
  44. # The has_writable_server and has_readable_server methods
  45. # were added in PyMongo 3.4.
  46. if not event.new_description.has_writable_server():
  47. logging.warning("No writable servers available.")
  48. if not event.new_description.has_readable_server():
  49. logging.warning("No readable servers available.")
  50. def closed(self, event):
  51. logging.info("Topology with id {0.topology_id} "
  52. "closed".format(event))

Connection monitoring and pooling events are also available. For example:

  1. class ConnectionPoolLogger(ConnectionPoolListener):
  2. def pool_created(self, event):
  3. logging.info("[pool {0.address}] pool created".format(event))
  4. def pool_cleared(self, event):
  5. logging.info("[pool {0.address}] pool cleared".format(event))
  6. def pool_closed(self, event):
  7. logging.info("[pool {0.address}] pool closed".format(event))
  8. def connection_created(self, event):
  9. logging.info("[pool {0.address}][conn #{0.connection_id}] "
  10. "connection created".format(event))
  11. def connection_ready(self, event):
  12. logging.info("[pool {0.address}][conn #{0.connection_id}] "
  13. "connection setup succeeded".format(event))
  14. def connection_closed(self, event):
  15. logging.info("[pool {0.address}][conn #{0.connection_id}] "
  16. "connection closed, reason: "
  17. "{0.reason}".format(event))
  18. def connection_check_out_started(self, event):
  19. logging.info("[pool {0.address}] connection check out "
  20. "started".format(event))
  21. def connection_check_out_failed(self, event):
  22. logging.info("[pool {0.address}] connection check out "
  23. "failed, reason: {0.reason}".format(event))
  24. def connection_checked_out(self, event):
  25. logging.info("[pool {0.address}][conn #{0.connection_id}] "
  26. "connection checked out of pool".format(event))
  27. def connection_checked_in(self, event):
  28. logging.info("[pool {0.address}][conn #{0.connection_id}] "
  29. "connection checked into pool".format(event))

Event listeners can also be registered per instance of MongoClient:

  1. client = MongoClient(event_listeners=[CommandLogger()])

Note that previously registered global listeners are automatically included when configuring per client event listeners. Registering a new global listener will not add that listener to existing client instances.

Note

Events are delivered synchronously. Application threads block waiting for event handlers (e.g. started()) to return. Care must be taken to ensure that your event handlers are efficient enough to not adversely affect overall application performance.

Warning

The command documents published through this API are not copies. If you intend to modify them in any way you must copy them in your event handler first.

pymongo.monitoring.``register(listener)

Register a global event listener.

Parameters:

class pymongo.monitoring.``CommandListener

Abstract base class for command listeners.

Handles CommandStartedEvent, CommandSucceededEvent, and CommandFailedEvent.

  • failed(event)

    Abstract method to handle a CommandFailedEvent.

    Parameters:
  • started(event)

    Abstract method to handle a CommandStartedEvent.

    Parameters:
  • succeeded(event)

    Abstract method to handle a CommandSucceededEvent.

    Parameters:

class pymongo.monitoring.``ServerListener

Abstract base class for server listeners. Handles ServerOpeningEvent, ServerDescriptionChangedEvent, and ServerClosedEvent.

New in version 3.3.

  • closed(event)

    Abstract method to handle a ServerClosedEvent.

    Parameters:
  • description_changed(event)

    Abstract method to handle a ServerDescriptionChangedEvent.

    Parameters:
  • opened(event)

    Abstract method to handle a ServerOpeningEvent.

    Parameters:

class pymongo.monitoring.``ServerHeartbeatListener

Abstract base class for server heartbeat listeners.

Handles ServerHeartbeatStartedEvent, ServerHeartbeatSucceededEvent, and ServerHeartbeatFailedEvent.

New in version 3.3.

class pymongo.monitoring.``TopologyListener

Abstract base class for topology monitoring listeners. Handles TopologyOpenedEvent, TopologyDescriptionChangedEvent, and TopologyClosedEvent.

New in version 3.3.

  • closed(event)

    Abstract method to handle a TopologyClosedEvent.

    Parameters:
  • description_changed(event)

    Abstract method to handle a TopologyDescriptionChangedEvent.

    Parameters:
  • opened(event)

    Abstract method to handle a TopologyOpenedEvent.

    Parameters:

class pymongo.monitoring.``ConnectionPoolListener

Abstract base class for connection pool listeners.

Handles all of the connection pool events defined in the Connection Monitoring and Pooling Specification: PoolCreatedEvent, PoolClearedEvent, PoolClosedEvent, ConnectionCreatedEvent, ConnectionReadyEvent, ConnectionClosedEvent, ConnectionCheckOutStartedEvent, ConnectionCheckOutFailedEvent, ConnectionCheckedOutEvent, and ConnectionCheckedInEvent.

New in version 3.9.

class pymongo.monitoring.``CommandStartedEvent(command, database_name, \args*)

Event published when a command starts.

Parameters:
  • command: The command document.
  • database_name: The name of the database this command was run against.
  • request_id: The request id for this operation.
  • connection_id: The address (host, port) of the server this command was sent to.
  • operation_id: An optional identifier for a series of related events.
  • command

    The command document.

  • command_name

    The command name.

  • connection_id

    The address (host, port) of the server this command was sent to.

  • database_name

    The name of the database this command was run against.

  • operation_id

    An id for this series of events or None.

  • request_id

    The request id for this operation.

class pymongo.monitoring.``CommandSucceededEvent(duration, reply, command_name, request_id, connection_id, operation_id)

Event published when a command succeeds.

Parameters:
  • duration: The command duration as a datetime.timedelta.
  • reply: The server reply document.
  • command_name: The command name.
  • request_id: The request id for this operation.
  • connection_id: The address (host, port) of the server this command was sent to.
  • operation_id: An optional identifier for a series of related events.
  • command_name

    The command name.

  • connection_id

    The address (host, port) of the server this command was sent to.

  • duration_micros

    The duration of this operation in microseconds.

  • operation_id

    An id for this series of events or None.

  • reply

    The server failure document for this operation.

  • request_id

    The request id for this operation.

class pymongo.monitoring.``CommandFailedEvent(duration, failure, \args*)

Event published when a command fails.

Parameters:
  • duration: The command duration as a datetime.timedelta.
  • failure: The server reply document.
  • command_name: The command name.
  • request_id: The request id for this operation.
  • connection_id: The address (host, port) of the server this command was sent to.
  • operation_id: An optional identifier for a series of related events.
  • command_name

    The command name.

  • connection_id

    The address (host, port) of the server this command was sent to.

  • duration_micros

    The duration of this operation in microseconds.

  • failure

    The server failure document for this operation.

  • operation_id

    An id for this series of events or None.

  • request_id

    The request id for this operation.

class pymongo.monitoring.``ServerDescriptionChangedEvent(previous_description, new_description, \args*)

Published when server description changes.

New in version 3.3.

  • new_description

    The new ServerDescription.

  • previous_description

    The previous ServerDescription.

  • server_address

    The address (host, port) pair of the server

  • topology_id

    A unique identifier for the topology this server is a part of.

class pymongo.monitoring.``ServerOpeningEvent(server_address, topology_id)

Published when server is initialized.

New in version 3.3.

  • server_address

    The address (host, port) pair of the server

  • topology_id

    A unique identifier for the topology this server is a part of.

class pymongo.monitoring.``ServerClosedEvent(server_address, topology_id)

Published when server is closed.

New in version 3.3.

  • server_address

    The address (host, port) pair of the server

  • topology_id

    A unique identifier for the topology this server is a part of.

class pymongo.monitoring.``TopologyDescriptionChangedEvent(previous_description, new_description, \args*)

Published when the topology description changes.

New in version 3.3.

class pymongo.monitoring.``TopologyOpenedEvent(topology_id)

Published when the topology is initialized.

New in version 3.3.

  • topology_id

    A unique identifier for the topology this server is a part of.

class pymongo.monitoring.``TopologyClosedEvent(topology_id)

Published when the topology is closed.

New in version 3.3.

  • topology_id

    A unique identifier for the topology this server is a part of.

class pymongo.monitoring.``ServerHeartbeatStartedEvent(connection_id)

Published when a heartbeat is started.

New in version 3.3.

  • connection_id

    The address (host, port) of the server this heartbeat was sent to.

class pymongo.monitoring.``ServerHeartbeatSucceededEvent(duration, reply, connection_id, awaited=False)

Fired when the server heartbeat succeeds.

New in version 3.3.

  • awaited

    Whether the heartbeat was awaited.

    If true, then duration() reflects the sum of the round trip time to the server and the time that the server waited before sending a response.

  • connection_id

    The address (host, port) of the server this heartbeat was sent to.

  • duration

    The duration of this heartbeat in microseconds.

  • reply

    An instance of IsMaster.

class pymongo.monitoring.``ServerHeartbeatFailedEvent(duration, reply, connection_id, awaited=False)

Fired when the server heartbeat fails, either with an “ok: 0” or a socket exception.

New in version 3.3.

  • awaited

    Whether the heartbeat was awaited.

    If true, then duration() reflects the sum of the round trip time to the server and the time that the server waited before sending a response.

  • connection_id

    The address (host, port) of the server this heartbeat was sent to.

  • duration

    The duration of this heartbeat in microseconds.

  • reply

    A subclass of Exception.

class pymongo.monitoring.``PoolCreatedEvent(address, options)

Published when a Connection Pool is created.

Parameters:
  • address: The address (host, port) pair of the server this Pool is attempting to connect to.

New in version 3.9.

  • address

    The address (host, port) pair of the server the pool is attempting to connect to.

  • options

    Any non-default pool options that were set on this Connection Pool.

class pymongo.monitoring.``PoolClearedEvent(address)

Published when a Connection Pool is cleared.

Parameters:
  • address: The address (host, port) pair of the server this Pool is attempting to connect to.

New in version 3.9.

  • address

    The address (host, port) pair of the server the pool is attempting to connect to.

class pymongo.monitoring.``PoolClosedEvent(address)

Published when a Connection Pool is closed.

Parameters:
  • address: The address (host, port) pair of the server this Pool is attempting to connect to.

New in version 3.9.

  • address

    The address (host, port) pair of the server the pool is attempting to connect to.

class pymongo.monitoring.``ConnectionCreatedEvent(address, connection_id)

Published when a Connection Pool creates a Connection object.

NOTE: This connection is not ready for use until the ConnectionReadyEvent is published.

Parameters:
  • address: The address (host, port) pair of the server this Connection is attempting to connect to.
  • connection_id: The integer ID of the Connection in this Pool.

New in version 3.9.

  • address

    The address (host, port) pair of the server this connection is attempting to connect to.

  • connection_id

    The ID of the Connection.

class pymongo.monitoring.``ConnectionReadyEvent(address, connection_id)

Published when a Connection has finished its setup, and is ready to use.

Parameters:
  • address: The address (host, port) pair of the server this Connection is attempting to connect to.
  • connection_id: The integer ID of the Connection in this Pool.

New in version 3.9.

  • address

    The address (host, port) pair of the server this connection is attempting to connect to.

  • connection_id

    The ID of the Connection.

class pymongo.monitoring.``ConnectionClosedReason

An enum that defines values for reason on a ConnectionClosedEvent.

New in version 3.9.

  • ERROR = ‘error’

    The connection experienced an error, making it no longer valid.

  • IDLE = ‘idle’

    The connection became stale by being idle for too long (maxIdleTimeMS).

  • POOL_CLOSED = ‘poolClosed’

    The pool was closed, making the connection no longer valid.

  • STALE = ‘stale’

    The pool was cleared, making the connection no longer valid.

class pymongo.monitoring.``ConnectionClosedEvent(address, connection_id, reason)

Published when a Connection is closed.

Parameters:
  • address: The address (host, port) pair of the server this Connection is attempting to connect to.
  • connection_id: The integer ID of the Connection in this Pool.
  • reason: A reason explaining why this connection was closed.

New in version 3.9.

  • address

    The address (host, port) pair of the server this connection is attempting to connect to.

  • connection_id

    The ID of the Connection.

  • reason

    A reason explaining why this connection was closed.

    The reason must be one of the strings from the ConnectionClosedReason enum.

class pymongo.monitoring.``ConnectionCheckOutStartedEvent(address)

Published when the driver starts attempting to check out a connection.

Parameters:
  • address: The address (host, port) pair of the server this Connection is attempting to connect to.

New in version 3.9.

  • address

    The address (host, port) pair of the server this connection is attempting to connect to.

class pymongo.monitoring.``ConnectionCheckOutFailedReason

An enum that defines values for reason on a ConnectionCheckOutFailedEvent.

New in version 3.9.

  • CONN_ERROR = ‘connectionError’

    The connection check out attempt experienced an error while setting up a new connection.

  • POOL_CLOSED = ‘poolClosed’

    The pool was previously closed, and cannot provide new connections.

  • TIMEOUT = ‘timeout’

    The connection check out attempt exceeded the specified timeout.

class pymongo.monitoring.``ConnectionCheckOutFailedEvent(address, reason)

Published when the driver’s attempt to check out a connection fails.

Parameters:
  • address: The address (host, port) pair of the server this Connection is attempting to connect to.
  • reason: A reason explaining why connection check out failed.

New in version 3.9.

  • address

    The address (host, port) pair of the server this connection is attempting to connect to.

  • reason

    A reason explaining why connection check out failed.

    The reason must be one of the strings from the ConnectionCheckOutFailedReason enum.

class pymongo.monitoring.``ConnectionCheckedOutEvent(address, connection_id)

Published when the driver successfully checks out a Connection.

Parameters:
  • address: The address (host, port) pair of the server this Connection is attempting to connect to.
  • connection_id: The integer ID of the Connection in this Pool.

New in version 3.9.

  • address

    The address (host, port) pair of the server this connection is attempting to connect to.

  • connection_id

    The ID of the Connection.

class pymongo.monitoring.``ConnectionCheckedInEvent(address, connection_id)

Published when the driver checks in a Connection into the Pool.

Parameters:
  • address: The address (host, port) pair of the server this Connection is attempting to connect to.
  • connection_id: The integer ID of the Connection in this Pool.

New in version 3.9.

  • address

    The address (host, port) pair of the server this connection is attempting to connect to.

  • connection_id

    The ID of the Connection.

Previous topic

mongo_replica_set_client – Tools for connecting to a MongoDB replica set

Next topic

operations – Operation class definitions

This Page

Quick search