Failed to parse field [host] of type [text] .. can't get text on a START_OBJECT at 1:974

Elastic Stack Logstash
1

My first question on this forum, so apologies for missing to post any detail. If I can also take this opportunity to say a big hello to everyone from a newbie to the world of Elastic Stack! :slight_smile:

I have a CSV file i am trying to send to logstash sourcing from both local input and via a filebeat - the exact same format. My filebeat config for local file input works. But the same file when coming in via filebeats (all v7.7) throws the error

error => "mapper_parsing_exception"
reason =>  "failed to parse field [host] of type [text] in documents with id 'blah blah'. Preview of field's value: '{name=my.host.name}'"
caused_by => "illegal state exception"
reason => "Can't get text on START_OBJECT at 1:974"

My logstash conf (conf.d/my-csv-data.conf)

input {
   file {
	   start_position => "beginning"
	   path => "/what/ever/*.csv"
   }
   beats {
	   id => "some-id"
	   port => 5044
   }
}
output {
   elasticsearch {
	   hosts => ["localhosts:9200"]
	   action => "index"
	   index => "myindex"
   }
}

The filebeat config is essentially a path added to the default filebeats.input.paths collecting *.csv and pointing to the above logstash host on port 5044. But as below, all the same:

filebeats,inputs:
- type: log
  enabled: true
  paths:
     - /path/to/data/*.csv
  tags: ["csv-type-x"]

- type: log
  enabled: true
  paths:
     - /other/path/to/data/*.csv
  tags: ["csv-type-y"]
  # etc etc
output.logstash:
   hosts: [ "logstashhost:5044"]
 # and the rest of the default stuff here

The CSV fields do not appear to be the problem when the file is processed locally (the hostname is populated properly too). I am wondering what could be different about the same data coming in through filebeats?

Any hints would be really appreciated!

2

Read this post.

1 Like
3

Thanks for this. This solved the problem for me.

However, if I can point out that I needed to correct the rename from below

if ! [host][name] { mutate { rename { "[host]" => "[host][name]" } } }

to

if ! [host][name] { mutate { rename { "[host]" => "%{[host][name]}" } } }

source: Logstash docs - Access Events data and fields in the configuration

And thank you for your prompt help :slight_smile:

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.