elasticsearch 使用Serilog进行ElasticSearch？

我正在尝试将Serilogger与Elasticsearch结合使用，但我不知道如何让它们一起工作

[2015-06-02 12:45:49,149][DEBUG][action.bulk              ] [Jimaine Szardos] [logstash-2015.06.02][4] failed to execute bulk item (index) index {[logstash-2015.06.02][logevent][AU2z4ILA3Y9Gz86fGG3z], source[{"@timestamp":"2015-06-02T12:45:43.4368603+02:00","level":"Information","messageTemplate":"Creating new Taxi {0}","message":"Creating new Taxi \"84/10749/18/27/80\"","fields":{"0":"84/10749/18/27/80","SourceContext":"Akka.Logger.Serilog.SerilogLogger"}}]}
org.elasticsearch.index.mapper.MapperParsingException: failed to parse [fields.0]
        at org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse(AbstractFieldMapper.java:409)
        at org.elasticsearch.index.mapper.object.ObjectMapper.serializeValue(ObjectMapper.java:706)
        at org.elasticsearch.index.mapper.object.ObjectMapper.parse(ObjectMapper.java:497)
        at org.elasticsearch.index.mapper.object.ObjectMapper.serializeObject(ObjectMapper.java:554)
        at org.elasticsearch.index.mapper.object.ObjectMapper.parse(ObjectMapper.java:487)
        at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:544)
        at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:493)
        at org.elasticsearch.index.shard.IndexShard.prepareCreate(IndexShard.java:453)
        at org.elasticsearch.action.bulk.TransportShardBulkAction.shardIndexOperation(TransportShardBulkAction.java:432)
        at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:149)
        at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:515)
        at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:422)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NumberFormatException: For input string: "84/10749/18/27/80"
        at java.lang.NumberFormatException.forInputString(Unknown Source)
        at java.lang.Long.parseLong(Unknown Source)
        at java.lang.Long.parseLong(Unknown Source)
        at org.elasticsearch.common.xcontent.support.AbstractXContentParser.longValue(AbstractXContentParser.java:145)
        at org.elasticsearch.index.mapper.core.LongFieldMapper.innerParseCreateField(LongFieldMapper.java:300)
        at org.elasticsearch.index.mapper.core.NumberFieldMapper.parseCreateField(NumberFieldMapper.java:236)
        at org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse(AbstractFieldMapper.java:399)
        ... 14 more

这似乎是日志条目的内容

[{
  "@timestamp":"2015-06-02T12:45:43.4368603+02:00", 
  "level":"Information",
  "messageTemplate":"Creating new Taxi {0}", 
  "message":"Creating new Taxi \"84/10749/18/27/80\"",
  "fields": {
       "0":"84/10749/18/27/80",
       "SourceContext":"Akka.Logger.Serilog.SerilogLogger"
  }
}]

---

出现此问题的原因是Serilog发布了格式错误的日志条目，还是这里发生了其他问题？

似乎

字段0

已映射为映射类型中的一个数字，

“84/10749/18/27/80”

无法转换为一个数字。能否显示此命令的输出？你有自定义映射还是让Serilog帮你处理的？

λcurl-XGET localhost:9200/logstash-2015.06.02//u mapping/logevent{“logstash-2015.06.02”：{“mappings”：{“logevent”：{“properties”：{“timestamp”：{“type”：“dateOptionalTime”}，“fields”：{“properties”：{“properties”：{“0”：{“type”：“long”}，“Message type”：“string”}，“SourceContext”：{“type”：“string”}}}，level:{“type”：“string”}，message:{“type”：“string”}，messageTemplate:{“type”：“string”}}

serilog已经创建了映射，我们开始了，

字段：{“properties”：{“0”：{“type”：“long”‌​}。您在使用吗？我在Serilog项目上提出了这个问题，以查看数字属性名称的状态-这些属性名称应由接收器处理。似乎
字段.0
已在映射类型中映射为一个数字，
“84/10749/18/27/80”
无法转换为数字。能否显示此命令的输出
curl-XGET localhost:9200/logstash-2015.06.02/_-mapping/logevent
？您是否有自定义映射或是否让Serilog为您处理它？
λcurl-XGET localhost:9200/logstash-2015.06.02//u-mapping/logevent{“logstash-2015.06.02”：{“mappings”：{“事件”：{“属性”：{“@timestamp”：{“类型”：“日期”，“格式”：“dateOptionalTime”}，“字段”：{“属性”：{“类型”：“长”}，“消息”：{“类型”：“字符串”}，“源上下文”：{“类型”：“字符串”}}，“级别”：{“类型”：“字符串”}，“消息”：{“类型”：“字符串”}，“消息模板”：{“类型”：“字符串”}}}
serilog{属性：{“0”：{“类型”：“长”‌​}。您在使用吗？我在Serilog项目上提出了这个问题，以查看数字属性名称的状态-这些属性名称应由接收器处理。似乎
字段.0
已在映射类型和
“84/10749/18/27/80中映射为一个数字“
无法转换为数字。能否显示此命令的输出
curl-XGET localhost:9200/logstash-2015.06.02/_-mapping/logevent
？您是否有自定义映射或是否让Serilog为您处理它？
λcurl-XGET localhost:9200/logstash-2015.06.02//u-mapping/logevent{“logstash-2015.06.02”：{“mappings”：{“logevent”：{“logevent”：{“属性”：{“@timestamp”：{“类型”：“日期”，“格式”：“dateOptionalTime”}，“字段”：{“属性”：{“类型”：“长”}，“消息”：{“类型”：“字符串”}，“源上下文”：{“类型”：“字符串”}}，“级别”：{“类型”：“字符串”}，“消息”：{“类型”：“字符串”}，“消息模板”：{“类型”：“字符串”}}}
serilog{属性：{“0”：{“类型”：“长”‌​}。您在使用吗？我在Serilog项目中提出了这个问题，以查看数字属性名称的状态-这些属性名称应该由接收器处理。