Should the fields.yml be deployed along with the lambda (I'm on AWS)? I added some custom fields to fields.yml and noticed they weren't added to the index mapping. I tried to explicitly set setup.template.fields=fields.yml in functionbeat.yml, but when I deployed that I kept getting exceptions in my lambda because it couldn't find fields.yml (the logs indicating it was looking for a path on my local machine). I see that fields.yml isn't included in the package.zip that is created - so I'm wondering if I've misconfigured something or if I'm not understanding how the fields config is used? It seems the function is meant to create the index and the mappings (not something I should normally do from my local machine), but maybe I'm wrong about that.
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.