Hi Emanuil,
Many thanks for the welcome and your reply!.
To answer on your questions quickly:
a. I do not know in advance the field names nor the structure.
b. They do not follow a predictable pattern.
To elaborate and some more background info:
The structure under the path of APP_AND_FORM_ATTRS.ArrayOfNameValue.NameValue.Value represent an app fields created by customers. This is completly dynamic. Each can create any number of apps with any numbers of fields, having any name and structure. The end users provide the name for the fields and cannot force them into a specific pattern (this are end users, none developers). Once an app is created, fields will keep the same as long as the app is not changed, but it can be changed at any point.
The idea is to create a seamless flow into elastic and we cannot relay on "index management" on customer side.
Thus, was going into the direction of pipeline, as can allow users to have a "configuration" settings for the fields they want to have as numbers in reports (kibana) and create the pipline.
I was looking into index template, and will look more into it - thanks, though it seems to be under the things we'de like to avoid under "index management".
Yet, looking at the issue as just as a pipline issue, and to better learn the stuck, would appreciate if you can help me understand why is the convert processing do not apply on the given sample.
Many thanks again for your reply, welcome and help.