Normally this is the raw data before lumberjack gets its hands on it. Normally lumberjack isn't doing anything other than adding a `@type` field though.

I think we may need a different import strategy for at least this test. Normally the log files contains the raw `@message` and the unit tests only appends a `@type` field and pushes it into redis. There's not currently a way to add an arbitrary field such as `source_latlon` when importing test data. We'll need to think about this.