Skip to content

Commit aae7635

Browse files
committed
EC last feedback
1 parent d7180a3 commit aae7635

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

source/monitoring/cluster-monitoring.txt

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,9 @@ Subscribe to Events
3838
You can access details about SDAM events by subscribing to them
3939
in your application. To subscribe to an event, define an Application
4040
Performance Monitoring (APM) callback function to handle each event
41-
type you want to subscribe to. Use a ``mongoc_apm_callbacks_t`` object
42-
to register the list of APM callbacks with a client using the
43-
``mongoc_client_set_apm_callbacks()`` function.
41+
type you want to subscribe to. Pass a ``mongoc_apm_callbacks_t`` object
42+
to the ``mongoc_client_set_apm_callbacks()`` function to register the
43+
list of APM callbacks with a client.
4444

4545
This code monitors server opening events by performing the following
4646
actions:
@@ -66,15 +66,13 @@ messages that resemble the following:
6666
.. code-block:: none
6767
:copyable: false
6868

69-
Server opening on ac-rmuag0v-shard-00-00.gh0qg50.mongodb.net:27017
70-
Server opening on ac-rmuag0v-shard-00-01.gh0qg50.mongodb.net:27017
71-
Server opening on ac-rmuag0v-shard-00-02.gh0qg50.mongodb.net:27017
69+
Server opening: <host>:<port number>
7270

7371
Event Descriptions
7472
------------------
7573

7674
You can subscribe to SDAM events by defining the corresponding
77-
event callback function. The following table provides the name of
75+
APM callback function. The following table provides the name of
7876
each SDAM event, links to the type's API documentation, and describes
7977
when the event is published:
8078

0 commit comments

Comments
 (0)