[SERVER-9278] Add counter for bad bson docs (from objCheck) Created: 08/Apr/13 Updated: 09/Apr/20 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Networking, Storage |
| Affects Version/s: | 2.4.1 |
| Fix Version/s: | features we're not sure of |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | metrics, move-sa, objecheck, stats | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Add counter to serverStatus.metrics for "network.incoming.documents.invalid". Would be good to count outgoing (errors) as well. Also, the total count in both directions. |
| Comments |
| Comment by Eric Milkie [ 11/Nov/16 ] |
|
BSON Validation has changed since Scott originally wrote this ticket. Is it still relevant? |
| Comment by Scott Hernandez (Inactive) [ 08/Apr/13 ] |
|
We don't exactly, but we do for other clients like mognos or replica set connections. I was more thinking in the case of getting a bson assertion (on mongod), which would be our attempt to read a corrupt/invalid doc. |
| Comment by Eric Milkie [ 08/Apr/13 ] |
|
When do we objcheck outgoing BSON? |