Mongodb fields missing values

Hi,

I have a mongodb collection hosted at mlab. Currently all documents have same fields. I’m getting all fields in Metabase but some of the fields are missing values. I get the same results with Metabase on AWS (Elastic Beanstalk) and local setup on MacOS.

Any ideas what I’m missing?

Sample document:

mlab:
{
“_id” : ObjectId(“5c958633e75279000d872c09”),
“log_count/INFO” : 61,
“start_time” : ISODate(“2019-03-23T01:00:32.941Z”),
“log_count/WARNING” : 1,
“memusage/startup” : 73404416,
“memusage/max” : 98537472,
“scheduler/enqueued/disk” : 356,
“scheduler/enqueued” : 356,
“scheduler/dequeued/disk” : 356,
“scheduler/dequeued” : 356,
“downloader/request_count” : 358,
“downloader/request_method_count/GET” : 358,
“downloader/request_bytes” : 124365,
“downloader/response_count” : 358,
“downloader/response_status_count/301” : 2,
“downloader/response_bytes” : 4088838,
“downloader/response_status_count/200” : 356,
“response_received_count” : 356,
“request_depth_max” : 2,
“dupefilter/filtered” : 238,
“item_scraped_count” : 287,
“finish_time” : ISODate(“2019-03-23T01:04:51.769Z”),
“finish_reason” : “finished”,
“name” : “rafha”
}
metabase:
{
“request_bytes”: null,
“enqueued/disk”: null,
“WARNING”: null,
“request_depth_max”: 2,
“filtered”: null,
“item_scraped_count”: 287,
“request_count”: null,
“max”: null,
“startup”: null,
“response_bytes”: null,
“response_status_count/301”: null,
“name”: “rafha”,
“dequeued”: null,
“enqueued”: null,
“request_method_count/GET”: null,
“response_count”: null,
“finish_time”: “2019-03-23T01:04:51.769Z”,
“dequeued/disk”: null,
“_id”: “5c958633e75279000d872c09”,
“response_received_count”: 356,
“INFO”: null,
“finish_reason”: “finished”,
“start_time”: “2019-03-23T01:00:32.941Z”,
“response_status_count/200”: null
}

OK,

Looking at the data this has surely something to do with the field names. Looks like “/” is making some havoc. Guess I will have to amend the field names at the source as a work around?