I'll try my best but you might want to wait for better answers
I do believe it's a mapping issue, here elestic is rejecting because the setting is not defined ?
You could also try to set the fields a keyword but it would be a static per field definition which can be tedious in case you have mixed data with a lot of fields.
Also there is a lot of ruby scripts around here if you want to extract the subkeys.
We were hoping of not having to maintain the mappings on the elastic level but perhaps we'll have to.
Would it be possible to parse it at the fluentbit level so that the second level is a string instead of a object? Just trying to work out if there is a best practise for us to follow
Yes ! That's the script i was thinking about you solved that from the parsing side.
I suggest you also check data types of your mapping ( which i believe is automatic ) So that you understand the type must match and can be conflicting or sometimes prevent the document from being ingested correctly by elastic.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.