I am working on a beat where the field names and types it returns are not known until run time. There is the option to use a custom index template so the user could build such an index template and add it to the beat config. However all the information to create an index template is available in the config file for the beat. Is it possible to modify the "export template" command to dynamically build the field list based on the current config file for the beat as opposed to pulling it from the static fields.yaml file?
I think that's a good idea. Please open an enhancement request. Pull requests would be welcome as well 
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.