-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Networking & Observability
-
N&O 2026-02-02, N&O 2026-03-02
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We will need to do some investigation into the best approach to take for this. Two potential approaches are:
- Add a mechanism that reads the FTDC and generates the bson objects to see how big they are (This is likely too costly fleet-wide)
- Add a server status parameter / FTDC parameter that tracks the FTDC size and is ingested by ingestion ping