[ https://issues.apache.org/jira/browse/FLAGON-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026410#comment-17026410 ]
Joshua Poore commented on FLAGON-483: ------------------------------------- looks like a indexing issue. From LogStash: [2020-01-30T02:58:53,581][WARN ][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. \{:status=>400, :action=>["index", {:_id=>nil, :_index=>"userale", :_type=>"doc", :routing=>nil}, #<LogStash::Event:0x281d598b>], :response=>\{"index"=>{"_index"=>"userale", "_type"=>"doc", "_id"=>"bHFj9G8BoZIUZ9d4Gw79", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"object mapping for [details] tried to parse field [details] as object, but found a concrete value"}}}} > userale.log & userale.packageCustomLog logs are not being indexed by ES > ----------------------------------------------------------------------- > > Key: FLAGON-483 > URL: https://issues.apache.org/jira/browse/FLAGON-483 > Project: Flagon > Issue Type: Bug > Components: UserALE.js > Affects Versions: UserALE.js 2.1.0 > Reporter: Joshua Poore > Assignee: Joshua Poore > Priority: Major > Fix For: UserALE.js 2.1.0 > > > New examples for .log and .packageCustomLog are generating logs, but logs are > not being indexed by ES back end. > * Logs are being generated and show expected structure via example logging > server > * 'raw' logs generated fromĀ -- This message was sent by Atlassian Jira (v8.3.4#803005)