Hello Dennis -
I don't see anything wrong with the JSON sample you posted. I was able to create a basic 'Receive JSON on a REST endpoint' Input and POST the sample to the GeoEvent Processor Input's REST endpoint.
Configuring my Input as shown in the first illustration below, I allowed a new GeoEvent Definition to be created. I've included an illustration of the generated GeoEvent Definition below. When I post the JSON, I get two events received. I can output those to a system text file as JSON without any problem.
I noticed that in the second record, the one whose driverID is 83886089, a few of the fields are null. If I delete the GeoEvent Definition and then swap the order of the events in the list so that the record with the null attributes is first ... the generated GeoEvent Definition does not contain fields for the attributes which were initially received as null.
I'm not sure, but it might be that you have a GeoEvent Definition which does not match the content discovered by the Input connector, so it discards the event it cannot recognize. That would explain why you are observing the event count not incrementing. You might try deleting your existing GeoEvent Definitions and seeing if the Input is able to create a new one based on data it receives.
The only other piece to the configuration that I notice is that your connector, aside from specifying connection credentials and a polling frequency, is specifying a 'Parameters' value of 'minutes=1440'. I'm not sure what that parameter is, or it is plays into the issue.