-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
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
- backports
-
DOCS-14956 Server [BACKPORT] [v5.0] Capture df (disk full) statistics in FTDC
- Closed
-
DOCS-14957 [server] [v4.2] Capture df (disk full) statistics in FTDC
- Closed
-
DOCS-14958 [server] [v4.4] Capture df (disk full) statistics in FTDC
- Closed
- documents
-
SERVER-28953 Capture df (disk full) statistics in FTDC
- Closed