admin管理员组文章数量:1244411
I am having issues with our AWS ecs -> fluentbit -> elasticsearch set up, specifically around nested json.
For example, if the log message is:
{
"endpoint": "/process",
"payload": {
"body": {
"success": "true",
"items": [
{"name": "item_one"},
{"name": "item_two"}
]
}
}
}
We would like the following fields to be parsed:
endpoint
-> "process"
payload
-> {"body": {"success": "true", "items": {"name": "item_one"}, {"name": "item_two"}]}
Only the top level key.
We set "index.mapping.depth.limit": 1 but this resulted in the logs being rejected by elasticsearch
"status":400,
"error":{
"type": "illegal_argument_exception",
"reason": "Limit of mapping depth [1] has been exceeded due to object field []"
}
Is there a setting that will parse only the top level but accept the rest of the data as the body in elasticsearch?
Or is this something that should be solved in the fluentbit level?
本文标签: fluent bitNested JSON parsing with elasticsearchStack Overflow
版权声明:本文标题:fluent bit - Nested JSON parsing with elasticsearch - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1740151040a2232661.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论