Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

object mapping for [ModifiedProperties] #15

Closed
borg333 opened this issue Nov 25, 2019 · 3 comments
Closed

object mapping for [ModifiedProperties] #15

borg333 opened this issue Nov 25, 2019 · 3 comments

Comments

@borg333
Copy link

borg333 commented Nov 25, 2019

i have this in beat's log
Nov 25 11:10:00 logstash logstash[103730]: [2019-11-25T11:10:00,543][WARN ][logstash.outputs.elasticsearch][main] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>"o365-2019.11.25", :_type=>"_doc", :routing=>nil}, #<LogStash::Event:0x322ca0c8>], :response=>{"index"=>{"_index"=>"o365-2019.11.25", "_type"=>"_doc", "_id"=>"7jycoW4BRbr-kt3SOEWj", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"object mapping for [ModifiedProperties] tried to parse field [null] as object, but found a concrete value"}}}}
and i dont know, its a logs problem or beat?

@chris-counteractive
Copy link
Collaborator

Thanks for the question, @borg333. We did see this issue (#14) and implemented a fix in v1.4.2. Are you using that latest version? If not, the fix is actually done in the config file, you could add the following line in your o365beat.yml:

processors:
  # all the rest of your existing processors section
  - convert:
      fields:
        # all the rest of your other convert.fields section
        - {from: ModifiedProperties, type: string}

If this doesn't fix the error, please let me know. I'll keep this open until we get your issue resolved. Thanks!

@borg333
Copy link
Author

borg333 commented Nov 26, 2019

@chris-counteractive o365beat is latest version and conf that you prived is already in yml

@borg333
Copy link
Author

borg333 commented Nov 26, 2019

seems ok now after creating a new index but new issue exists.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants