Missing fields in status json spec

It seems like in spec `cluster.layers` is missing a field named `backup`.
i.e.
```
"layers": {
"_valid": true,
"backup": {
"blob_recent_io": {
"bytes_per_second": 0,
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
},
"instances": {
"1254b00eead1dd0e7b8b24746b5ed4fb": {
"blob_stats": {
"recent": {
"bytes_per_second": 0,
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
},
"total": {
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
}
},
"configured_workers": 10,
"id": "1254b00eead1dd0e7b8b24746b5ed4fb",
"last_updated": 1590779093.3083599,
"main_thread_cpu_seconds": 22149.909,
"memory_usage": 1463214080,
"process_cpu_seconds": 28348.906999999999,
"resident_size": 1181474816,
"version": "6.2.15"
},
"15afb2802593f3851b6e6af93e0fb021": {
"blob_stats": {
"recent": {
"bytes_per_second": 0,
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
},
"total": {
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
}
},
"configured_workers": 10,
"id": "15afb2802593f3851b6e6af93e0fb021",
"last_updated": 1590779041.4182842,
"main_thread_cpu_seconds": 22531.102999999999,
"memory_usage": 1450610688,
"process_cpu_seconds": 28862.276000000002,
"resident_size": 1168699392,
"version": "6.2.15"
},
"1a726f8f81b5b703055e19c12c33e1cb": {
"blob_stats": {
"recent": {
"bytes_per_second": 0,
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
},
"total": {
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
}
},
"configured_workers": 10,
"id": "1a726f8f81b5b703055e19c12c33e1cb",
"last_updated": 1590779092.3042936,
"main_thread_cpu_seconds": 21436.459999999999,
"memory_usage": 1456705536,
"process_cpu_seconds": 27527.832999999999,
"resident_size": 1174851584,
"version": "6.2.15"
},
"8e506e2d1b7038b790cde81125679170": {
"blob_stats": {
"recent": {
"bytes_per_second": 0,
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
},
"total": {
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
}
},
"configured_workers": 10,
"id": "8e506e2d1b7038b790cde81125679170",
"last_updated": 1590779024.2851148,
"main_thread_cpu_seconds": 22281.098000000002,
"memory_usage": 1405464576,
"process_cpu_seconds": 28353.434000000001,
"resident_size": 1123672064,
"version": "6.2.15"
},
"da482523129734721341e5f8a7fbca20": {
"blob_stats": {
"recent": {
"bytes_per_second": 0,
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
},
"total": {
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
}
},
"configured_workers": 10,
"id": "da482523129734721341e5f8a7fbca20",
"last_updated": 1590779060.3107851,
"main_thread_cpu_seconds": 22591.386000000002,
"memory_usage": 1468559360,
"process_cpu_seconds": 28757.588,
"resident_size": 1186619392,
"version": "6.2.15"
},
"ed7de0a796d9311681ba8558b8fa775b": {
"blob_stats": {
"recent": {
"bytes_per_second": 0,
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
},
"total": {
"bytes_sent": 0,
"requests_failed": 0,
"requests_successful": 0
}
},
"configured_workers": 10,
"id": "ed7de0a796d9311681ba8558b8fa775b",
"last_updated": 1590779085.9744449,
"main_thread_cpu_seconds": 23071.764999999999,
"memory_usage": 1419898880,
"process_cpu_seconds": 29326.712,
"resident_size": 1138003968,
"version": "6.2.15"
}
},
"instances_running": 6,
"last_updated": 1590779093.3083599,
"paused": false,
"tags": {
"default": {
"current_container": "file:///mnt/backup/fdb/gcppreprod1fdb1/backup-2020-05-29-16-58-25.997459",
"current_status": "has been completed",
"last_restorable_seconds_behind": 7153.6038669999998,
"last_restorable_version": 23133562234055,
"mutation_log_bytes_written": 105289395,
"mutation_stream_id": "ab83cf300ad34ca155724779099d796f",
"range_bytes_written": 130170963595,
"running_backup": false,
"running_backup_is_restorable": false
}
},
"total_workers": 60
}
},

The issue identifies the cluster.layers section of the status JSON spec and shows the expected backup structure. Start by locating the status JSON specification and checking how other layer fields are defined. Done means the backup field and its shown structure are represented accurately in the spec, with relevant validation passing.

Written by the indexing model from the issue text.