Server-side remediation for incoming sensor data

1. One or more non-transitory computer-readable media of a data processing platform that includes a plurality of data processing microservices, the one or more non-transitory computer-readable media storing computer-executable instructions that upon execution cause one or more processors to perform acts comprising:

receiving incoming sensor data from a data collection device at the data processing platform, wherein the data processing platform includes the plurality of data processing microservices;

detecting that the incoming sensor data from the data collection device caused an error at a data processing microservice of the data processing platform;

queueing the incoming sensor data in a faulty data cache of the data processing platform;

modifying source code of at least one of the data processing microservice or the incoming sensor data stored in the faulty data cache such that the incoming sensor data is processed by the data processing microservice without the error; and

deleting the incoming sensor data from the faulty data cache of the data processing platform.

2. The one or more non-transitory computer-readable media of claim 1 , wherein the acts further comprise, following the detection of the error at the data processing microservice:

determining whether the error experienced by the data processing microservice caused a lock up of the data collection device; and

in response to the determination that the error caused the lock up of the data collection device, directing the data collection device to resume a work operation state that frees up the data collection device to collect additional sensor data for uploading to the data processing platform.

3. The one or more non-transitory computer-readable media of claim 1 , wherein the acts further comprise, following the detection of the error at the data processing microservice:

generating a data error event entry in a data error event queue documenting the error associated with the incoming sensor data; and

removing the data error event entry in from the data error event queue following processing of the incoming sensor data without error by the data processing microservice of the data processing platform.

4. The one or more non-transitory computer-readable media of claim 1 , wherein the acts further comprise:

generating a status notification that includes a device identifier of the data collection device, the status notification indicating that the error occurred during processing of the incoming sensor data from the data collection device; and

providing the status notification that includes the device identifier for presentation via an application interface.

5. The one or more non-transitory computer-readable media of claim 4 , wherein the acts further comprise:

determining a user identifier of a user assigned to the data collection device based at least on metadata embedded in the incoming sensor data; and

providing the user identifier along with the device identifier in the status notification that is presented via the application interface.

6. The one or more non-transitory computer-readable media of claim 5 , wherein the acts further comprising:

generating a new status notification that includes at least one of the device identifier of the data collection device or the user identifier of the user indicating that the error associated with the processing of the incoming sensor data is resolved; and

providing the new status notification for the presentation via the application interface.

7. The one or more non-transitory computer-readable media of claim 4 , wherein the status notification is included in an administrative report that is presented to an administrator of the data processing platform or a user report that is presented to an authorized user of the data processing platform.

8. The one or more non-transitory computer-readable media of claim 1 , wherein the modifying the source code of the data processing microservice includes:

modifying the source code of the data processing microservice that experienced the error while processing the incoming sensor data; and

reprocessing the incoming sensor data via the data processing microservice that includes the modified source code.

9. The one or more non-transitory computer-readable media of claim 1 , wherein the modifying the incoming sensor data includes:

applying a modification to the incoming sensor data received from the data collection device and stored in the faulty data cache;

storing data regarding the modification of the incoming sensor data in a chain-of-custody ledger; and

reprocessing the incoming sensor data that includes the modification via the data processing microservice.

10. The one or more non-transitory computer-readable media of claim 9 , wherein the data regarding the modification as stored in the chain-of-custody ledger includes a first digital signature of a first data file that includes the incoming sensor data and a second digital signature of a second data file that includes modified incoming sensor data.

11. A system, comprising:

one or more processors; and

memory including a plurality of computer-executable components that are executable by the one or more processors to perform a plurality of actions, the plurality of actions comprising:

receiving incoming sensor data from a data collection device at a data processing platform, wherein the data processing platform includes a plurality of data processing microservices;

detecting, via an error management microservice of the data processing microservice, that the incoming sensor data from the data collection device caused an error at the data processing microservice;

queueing, via the error management microservice, the incoming sensor data in a faulty data cache of the data processing platform;

modifying, via the error management microservice, source code of at least one of the data processing microservice or the incoming sensor data stored in the faulty data cache such that the incoming sensor data is processed by the data processing microservice without the error; and

deleting, via the error management microservice, the incoming sensor data from the faulty data cache of the data processing platform.

12. The system of claim 11 , wherein the actions further comprise, following the detection of the error at the data processing microservice:

determining whether the error experienced by the data processing microservice caused a lock up of the data collection device; and

in response to the determination that the error caused the lock up of the data collection device, directing the data collection device to resume a work operation state that frees up the data collection device to collect additional sensor data for uploading to the data processing platform.

13. The system of claim 11 , wherein the actions further comprise, following the detection of the error at the data processing microservice:

generating a data error event entry in a data error event queue documenting the error associated with the incoming sensor data; and

removing the data error event entry in from the data error event queue following processing of the incoming sensor data without error by the data processing microservice of the data processing platform.

14. The system of claim 11 , wherein the actions further comprise:

generating a status notification that includes a device identifier of the data collection device, the status notification indicating that the error occurred during processing of the incoming sensor data from the data collection device; and

providing the status notification that includes the device identifier for presentation via an application interface.

15. The system of claim 14 , wherein the actions further comprise:

determining a user identifier of a user assigned to the data collection device based at least on metadata embedded in the incoming sensor data; and

providing the user identifier along with the device identifier in the status notification that is presented via the application interface.

16. The system of claim 14 , wherein the status notification is included in an administrative report that is presented to an administrator of the data processing platform or a user report that is presented to an authorized user of the data processing platform.

17. A computer-implemented method, comprising:

receiving incoming sensor data from a data collection device at a data processing platform, wherein the data processing platform includes a plurality of data processing microservices;

detecting, via an error management microservice of the data processing microservice, that the incoming sensor data from the data collection device caused an error at the data processing microservice;

queueing, via the error management microservice, the incoming sensor data in a faulty data cache of the data processing platform;

modifying, via the error management microservice, source code of at least one of the data processing microservice or the incoming sensor data stored in the faulty data cache such that the incoming sensor data is processed by the data processing microservice without the error; and

deleting, via the error management microservice, the incoming sensor data from the faulty data cache of the data processing platform.

18. The computer-implemented method of claim 17 , wherein the modifying the source code of the data processing microservice includes:

modifying the source code of the data processing microservice that experienced the error while processing the incoming sensor data; and

reprocessing the incoming sensor data via the data processing microservice that includes the modified source code.

19. The computer-implemented method of claim 17 , wherein the modifying the incoming sensor data includes:

applying a modification to the incoming sensor data received from the data collection device and stored in the faulty data cache;

storing data regarding the modification of the incoming sensor data in a chain-of-custody ledger; and

reprocessing the incoming sensor data that includes the modification via the data processing microservice.

20. The computer-implemented method of claim 19 , wherein the data regarding the modification as stored in the chain-of-custody ledger includes a first digital signature of a first data file that includes the incoming sensor data and a second digital signature of a second data file that includes modified incoming sensor data.