[DOCS-14921] Investigate changes in SERVER-28953: Capture df (disk full) statistics in FTDC Created: 09/Nov/21  Updated: 13/Nov/23  Resolved: 25/Jan/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.2.18, 5.2.0, 4.4.11, 5.0.6, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ian Fogelman
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backports DOCS-14956 Server [BACKPORT] [v5.0] Capture df (... Closed
backports DOCS-14957 [server] [v4.2] Capture df (disk full... Closed
backports DOCS-14958 [server] [v4.4] Capture df (disk full... Closed
Documented
documents SERVER-28953 Capture df (disk full) statistics in ... Closed
Participants:
Days since reply: 2 years, 2 weeks, 1 day ago
Epic Link: DOCSP-17171

 Description   
Downstream Change Summary

Docs to document that there is a new FTDC element on linux only platform only:

db.runCommand("getDiagnosticData").data.systemMetrics.mounts
{
	"/dev" : {
		"capacity" : NumberLong("33628246016"),
		"available" : NumberLong("33628246016"),
		"free" : NumberLong("33628246016")
	},
	"/run" : {
		"capacity" : NumberLong("6736269312"),
		"available" : NumberLong("6731268096"),
		"free" : NumberLong("6731268096")
	},
	"/" : {
		"capacity" : NumberLong("840696987648"),
		"available" : NumberLong("494027931648"),
		"free" : NumberLong("494027931648")
	},
	"/dev/shm" : {
		"capacity" : NumberLong("33681342464"),
		"available" : NumberLong("32035008512"),
		"free" : NumberLong("32035008512")
	},
	"/run/lock" : {
		"capacity" : 5242880,
		"available" : 5238784,
		"free" : 5238784
	},
...

Description of Linked Ticket

As we now collect also system metrics in the diagnostic data, it would be sometimes useful to know how full a disk was (or, in particular, whether it was 100% full).

Edit (JamesB): this would be most useful as <bytes available> / <bytes total>, not a percentage



 Comments   
Comment by Ian Fogelman [ 25/Jan/22 ]

db.runCommand(“getDiagnosticData”) is currently undocumented in the server corpus and looks like an internal command. Closing this and backport tickets as a Wont Fix.

Comment by PM Bot [ 09/Nov/21 ]

Downstream changes updated for upstream SERVER-28953:
Docs to document that there is a new FTDC element on linux only platform only:

db.runCommand("getDiagnosticData").data.systemMetrics.mounts
{
	"/dev" : {
		"capacity" : NumberLong("33628246016"),
		"available" : NumberLong("33628246016"),
		"free" : NumberLong("33628246016")
	},
	"/run" : {
		"capacity" : NumberLong("6736269312"),
		"available" : NumberLong("6731268096"),
		"free" : NumberLong("6731268096")
	},
	"/" : {
		"capacity" : NumberLong("840696987648"),
		"available" : NumberLong("494027931648"),
		"free" : NumberLong("494027931648")
	},
	"/dev/shm" : {
		"capacity" : NumberLong("33681342464"),
		"available" : NumberLong("32035008512"),
		"free" : NumberLong("32035008512")
	},
	"/run/lock" : {
		"capacity" : 5242880,
		"available" : 5238784,
		"free" : 5238784
	},
...

Generated at Thu Feb 08 08:11:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.