-
Notifications
You must be signed in to change notification settings - Fork 33
/
Copy pathconnection-monitoring.txt
321 lines (254 loc) · 7.01 KB
/
connection-monitoring.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
.. _golang-connection-monitoring:
=====================
Connection Monitoring
=====================
.. facet::
:name: genre
:values: reference
.. meta::
:keywords: code example, performance, monitor
:description: Monitor the Mongo DB Go Driver's connection pool by subscribing to connection pool events to optimize performance and understand the client lifecycle.
.. contents:: On this page
:local:
:backlinks: none
:depth: 2
:class: singlecols
Overview
--------
This guide shows you how to use the {+driver-short+} to monitor the
driver's connection pool. A connection pool is a set of open
Transmission Control Protocol (TCP) connections that your driver
maintains with a MongoDB instance. Connection pools help reduce the
number of new connections your application needs to create,
which might make your application run faster.
You might use information about connection pool events in your
application to optimize performance or understand the client lifecycle.
Subscribe to Events
-------------------
You can access details about connection pool events by subscribing to them
in your application. The following example demonstrates how to subscribe
to the ``PoolEvent`` event by instantiating a
``PoolMonitor`` and connecting to a deployment:
.. code-block:: go
var eventArray []*event.PoolEvent
cxnMonitor := &event.PoolMonitor{
Started: func(e *event.PoolEvent) {
eventArray = append(eventArray, e)
},
}
clientOpts := options.Client().ApplyURI(uri).SetPoolMonitor(cxnMonitor)
client, err := mongo.Connect(clientOpts)
Event Descriptions
------------------
The following table describes the types of pool events that the driver
emits:
.. list-table::
:widths: 33 67
:header-rows: 1
* - Pool Event Type
- Description
* - ``ConnectionPoolCreated``
- Created when a connection pool is created.
* - ``ConnectionPoolReady``
- Created when a connection pool is ready.
* - ``ConnectionPoolCleared``
- Created when all the connections in the pool are closed.
* - ``ConnectionPoolClosed``
- Created when a connection pool is closed, before the destruction of
the server instance.
* - ``ConnectionCreated``
- Created when a connection is created, but not necessarily
when it is used for an operation.
* - ``ConnectionReady``
- Created after a connection completes a
handshake and is ready to be used for operations.
* - ``ConnectionClosed``
- Created when a connection is closed.
* - ``ConnectionCheckOutStarted``
- Created when an operation attempts to acquire a connection for
execution.
* - ``ConnectionCheckOutFailed``
- Created when an operation cannot acquire a connection for
execution.
* - ``ConnectionCheckedOut``
- Created when an operation successfully acquires a connection for
execution.
* - ``ConnectionCheckedIn``
- Created when a connection is checked back into the pool after an operation
is executed.
Example Event Documents
-----------------------
The following sections show sample output for each type of connection
pool monitoring event.
ConnectionPoolCreated
~~~~~~~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionPoolCreated",
"address": "...",
"connectionId": 0,
"options": {
"maxPoolSize": 100,
"minPoolSize": 0,
"maxIdleTimeMS": 0
},
"reason": "",
"serviceId": null,
"error": null
}
ConnectionPoolReady
~~~~~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionPoolReady",
"address": "...",
"connectionId": 0,
"options": null,
"reason": "",
"serviceId": null,
"error": null
}
ConnectionPoolCleared
~~~~~~~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionPoolCleared",
"address": "...",
"connectionId": 0,
"options": null,
"reason": "",
"serviceId": null,
"error": null
}
ConnectionPoolClosed
~~~~~~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionPoolClosed",
"address": "...",
"connectionId": 0,
"options": null,
"reason": "",
"serviceId": null,
"error": null
}
ConnectionCreated
~~~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionCreated",
"address": "...",
"connectionId": 1,
"options": null,
"reason": "",
"serviceId": null,
"error": null
}
ConnectionReady
~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionReady",
"address": "...",
"connectionId": 1,
"options": null,
"reason": "",
"serviceId": null,
"error": null
}
ConnectionClosed
~~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionClosed",
"address": "...",
"connectionId": 1,
"options": null,
"reason": "",
"serviceId": null,
"error": null
}
ConnectionCheckOutStarted
~~~~~~~~~~~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionCheckOutStarted",
"address": "...",
"connectionId": 0,
"options": null,
"reason": "",
"serviceId": null,
"error": null
}
ConnectionCheckOutFailed
~~~~~~~~~~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionCheckOutFailed",
"address": "...",
"connectionId": 0,
"options": null,
"reason": "",
"serviceId": null,
"error": null
}
ConnectionCheckedOut
~~~~~~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionCheckedOut",
"address": "...",
"connectionId": 1,
"options": null,
"reason": "",
"serviceId": null,
"error": null
}
ConnectionCheckedIn
~~~~~~~~~~~~~~~~~~~
.. code-block:: none
:copyable: false
*event.PoolEvent
{
"type": "ConnectionCheckedIn",
"address": "...",
"connectionId": 1,
"options": null,
"reason": "",
"serviceId": null,
"error": null
}
Additional Information
----------------------
To learn more about monitoring a MongoDB deployment, see the :website:`How
to Monitor MongoDB
</basics/how-to-monitor-mongodb-and-what-metrics-to-monitor>` article.
To learn more about connecting to MongoDB, see the
:ref:`golang-connection-guide`.
API Documentation
~~~~~~~~~~~~~~~~~
To learn more about the methods and types mentioned in this
guide, see the following API documentation:
- `PoolMonitor <{+api+}/event#PoolMonitor>`__ type
- `PoolEvent <{+api+}/event#PoolEvent>`__ type
- `SetPoolMonitor() <{+api+}/mongo/options#ClientOptions.SetPoolMonitor>`__ method