Hi Mustafa,
- can you verify if the "*mergeMetaData*" property in the parser json is set to "*true*". - If this property is set to false, other fields won't be merged as meta data. - If this property is not set, it should default to true for the message strategy "ENVELOPE". - Any other behaviour is probably a bug. - Also verify if you set "*rawMessageStrategy*" to "*true*" for the same reasons. Best, Stefan On Wed, Feb 27, 2019 at 5:34 AM Mustafa Akmal <[email protected]> wrote: > Hello > I am using a CSV parser. I have the following log > {"data": "1,john,23","AdditionField": "abcd","AdditionField2": "12345"} > > Now I have set the raw message strategy to 'ENVELOPE' and the messageField > to 'data' > However after the record is indexed in elasticsearch, the parser does > parse the value inside data but it does not get the additional fields as > shown in the original log that is 'AdditionField' and 'AdditionField2'. > What am I doing wrong? Can anyone help? > Thanks! > > [image: Sent from Mailspring] > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > Virus-free. > www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <#m_-9076012844472627488_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- Stefan Kupstaitis-Dunkler https://datahovel.com/ https://twitter.com/StefanDunkler
