Skip to content

Commit e22a6c7

Browse files
mungitoperritojeff-allen-mongo
authored andcommitted
DOCSP-18660 Remove redundant note from serverStatus
1 parent 301fc3b commit e22a6c7

File tree

3 files changed

+0
-206
lines changed

3 files changed

+0
-206
lines changed

source/includes/extracts-server-status-projection-base.yaml

-188
Original file line numberDiff line numberDiff line change
@@ -11,192 +11,4 @@ content: |
1111
field and set it to ``1`` in the command. To exclude fields that are
1212
included by default, specify the top-level field and set to ``0`` in
1313
the command.
14-
---
15-
ref: _serverStatus-output-changes
16-
content: |
17-
18-
- Starting in MongoDB 5.0, {{operationName}}:
19-
20-
- Added new metrics to track use of Aggregation Pipeline methods:
21-
22-
- :serverstatus:`metrics.commands.update.pipeline`
23-
24-
- :serverstatus:`metrics.commands.findAndModify.pipeline`
25-
26-
- Added new metrics to track use of arrayFilter methods:
27-
28-
- :serverstatus:`metrics.commands.update.arrayFilters`
29-
30-
- :serverstatus:`metrics.commands.findAndModify.arrayFilters`
31-
32-
- Added new metric to track number of times ``newlyAdded`` fields
33-
were automatically removed:
34-
35-
- :serverstatus:`metrics.repl.reconfig.numAutoReconfigsForRemovalOfNewlyAddedFields`
36-
37-
- Replaced :serverstatus:`opReadConcernCounters` with
38-
:serverstatus:`readConcernCounters` to track use of read concern
39-
levels specified by query operations
40-
41-
- Added new metric to track number of incoming connections:
42-
43-
- :serverstatus:`connections.threaded`
44-
45-
- Added new metric to track resharding operations:
46-
47-
- :serverstatus:`shardingStatistics.resharding`
48-
49-
- Added new metric to track service executors:
50-
51-
- :serverstatus:`network.serviceExecutors`
52-
53-
- Added new metrics to track cursors:
54-
55-
- :serverstatus:`metrics.cursor.moreThanOneBatch`
56-
57-
- :serverstatus:`metrics.cursor.totalOpened`
58-
59-
- Added new metric to track hello commands:
60-
61-
- :serverstatus:`connections.exhaustHello`
62-
63-
- Starting in MongoDB 4.4, {{operationName}}:
64-
65-
- Added new metrics to track write concern failures caused
66-
by a custom global default write concern:
67-
68-
- :serverstatus:`metrics.getLastError.default`
69-
70-
- :serverstatus:`metrics.getLastError.default.unsatisfiable`
71-
72-
- :serverstatus:`metrics.getLastError.default.wtimeouts`
73-
74-
- Added new metrics to track authentication mechanism usage:
75-
76-
- :serverstatus:`security.authentication.mechanisms`
77-
78-
Each field in :serverstatus:`security.authentication.mechanisms`
79-
represents an authentication mechanism supported by your
80-
:binary:`~bin.mongod` / :binary:`~bin.mongos` instance, and
81-
includes information on the number of times that mechanism
82-
has been used.
83-
84-
These metrics are also available starting in MongoDB
85-
4.2.6 and 4.0.19.
86-
87-
- Added new topology metrics in :serverstatus:`connections`:
88-
89-
- :serverstatus:`connections.exhaustIsMaster`
90-
91-
- :serverstatus:`connections.awaitingTopologyChanges`
92-
93-
- Added new metrics to track slow DNS and SSL handshake operations
94-
in :serverstatus:`network`:
95-
96-
- :serverstatus:`network.numSlowDNSOperations`
97-
98-
- :serverstatus:`network.numSlowSSLOperations`
99-
100-
- Added new sync source metrics in :serverstatus:`metrics.repl`:
101-
102-
- :serverstatus:`metrics.repl.network.oplogGetMoresProcessed`
103-
104-
- :serverstatus:`metrics.repl.network.oplogGetMoresProcessed.num`
105-
106-
- :serverstatus:`metrics.repl.network.oplogGetMoresProcessed.totalMillis`
107-
108-
- :serverstatus:`metrics.repl.network.replSetUpdatePosition.num`
109-
110-
- :serverstatus:`metrics.repl.syncSource.numSelections`
111-
112-
- :serverstatus:`metrics.repl.syncSource.numTimesChoseSame`
113-
114-
- :serverstatus:`metrics.repl.syncSource.numTimesChoseDifferent`
115-
116-
- :serverstatus:`metrics.repl.syncSource.numTimesCouldNotFind`
117-
118-
- Added new metrics to track aggregation pipeline stage use in
119-
:serverstatus:`metrics.aggStageCounters`.
120-
121-
- Added new metrics to track queries that perform a collection scan:
122-
123-
- :serverstatus:`metrics.queryExecutor.collectionScans`
124-
- :serverstatus:`metrics.queryExecutor.collectionScans.nonTailable`
125-
- :serverstatus:`metrics.queryExecutor.collectionScans.total`
126-
127-
- Added new :serverstatus:`range deletion metrics
128-
<shardingStatistics.rangeDeleterTasks>` in
129-
:serverstatus:`shardingStatistics`.
130-
131-
- Starting in MongoDB 4.2.2, {{operationName}}:
132-
133-
- Added new transaction metrics in :serverstatus:`transactions` for
134-
:binary:`~bin.mongos`:
135-
136-
- :serverstatus:`transactions.currentOpen`
137-
138-
- :serverstatus:`transactions.currentActive`
139-
140-
- :serverstatus:`transactions.currentInactive`
141-
142-
- Starting in MongoDB 4.2.1 (and 4.0.13), {{operationName}} includes:
143-
144-
- :ref:`electionMetrics <server-status-electionMetrics>`
145-
146-
- Starting in MongoDB 4.2, {{operationName}}:
147-
148-
- Returns :serverstatus:`opcounters` and
149-
:serverstatus:`opcountersRepl` metrics as 64-bit integers (i.e.
150-
NumberLong) instead of 32-bit integers (i.e. NumberInt).
151-
152-
- Includes ``trafficRecording`` metrics in its output.
153-
154-
- Added new document count (``countDocs``) metrics in
155-
:serverstatus:`shardingStatistics`.
156-
157-
- Added new unacknowledged writes counts to
158-
:serverstatus:`metrics.repl.network`.
159-
160-
- Added new user operations counts to
161-
:serverstatus:`metrics.repl.stepDown`.
162-
163-
- Added new transaction metrics in :serverstatus:`transactions` for
164-
:binary:`~bin.mongod`.
165-
166-
- Includes :serverstatus:`transactions` metrics for
167-
:binary:`~bin.mongos`.
168-
169-
- Added
170-
:serverstatus:`~logicalSessionRecordCache.sessionCatalogSize`
171-
metric to :serverstatus:`logicalSessionRecordCache`.
172-
173-
- Added
174-
:serverstatus:`~shardingStatistics.countDonorMoveChunkLockTimeout`
175-
metric to :serverstatus:`shardingStatistics`.
176-
177-
- Added ``ReplicationStateTransition`` lock information to
178-
:serverstatus:`locks`.
179-
180-
- Reports ``ParallelBatchWriterMode`` lock information separately from
181-
``Global`` lock information. See :serverstatus:`locks`.
182-
183-
- Starting in MongoDB 4.0.6, {{operationName}} includes:
184-
185-
- :serverstatus:`opReadConcernCounters`
186-
187-
- :serverstatus:`opWriteConcernCounters` (Requires
188-
:parameter:`reportOpWriteConcernCountersInServerStatus` parameter
189-
set to ``true``).
190-
191-
- :serverstatus:`metrics.repl.apply.batchSize`
192-
193-
- Starting in MongoDB 4.0, {{operationName}} includes
194-
:serverstatus:`shardingStatistics` in its output.
195-
196-
- Starting in MongoDB 3.6, {{operationName}} no longer outputs the
197-
``rangeDeleter`` section.
198-
199-
- Starting in MongoDB 3.0, {{operationName}} no longer outputs the
200-
``workingSet``, ``indexCounters``, and ``recordStats`` sections.
201-
20214
...

source/includes/extracts-server-status-projection.yaml

-14
Original file line numberDiff line numberDiff line change
@@ -12,20 +12,6 @@ inherit:
1212
replacement:
1313
operationName: ":method:`db.serverStatus()`"
1414
---
15-
ref: serverStatus-command-output-change
16-
inherit:
17-
ref: _serverStatus-output-changes
18-
file: extracts-server-status-projection-base.yaml
19-
replacement:
20-
operationName: ":dbcommand:`serverStatus`"
21-
---
22-
ref: serverStatus-method-output-change
23-
inherit:
24-
ref: _serverStatus-output-changes
25-
file: extracts-server-status-projection-base.yaml
26-
replacement:
27-
operationName: ":method:`db.serverStatus()`"
28-
---
2915
ref: serverStatus-opWriteConcernCounters
3016
content: |
3117

source/reference/command/serverStatus.txt

-4
Original file line numberDiff line numberDiff line change
@@ -5672,7 +5672,3 @@ watchdog
56725672
The value set by :parameter:`watchdogPeriodSeconds`. This is the
56735673
period between status checks.
56745674

5675-
Output Changelog
5676-
----------------
5677-
5678-
.. include:: /includes/extracts/serverStatus-command-output-change.rst

0 commit comments

Comments
 (0)