Consider this snippet of an 0.1.0/manifest.yml example:
policy_templates:
- name: apm
inputs:
- type: traces
vars:
- name: host
type: int
title: APM Server port
required: true
show_user: true
default: 8200
If my data stream(s) don't have a streams key, the generated policy will just have an input with streams: [], and the variable host will not be there even if I had filled it in the UI.
For apm-server we don't have streams, so we need that the vars defined at the policy level get picked up and rendered in the generated policy.
Not sure on which repo this issue belongs, let me know if it should be transferred to Kibana.
Update: The ideal way forward is that the top level config shows right under inputs, and not under a streams entry. For this we need hbs templates at the top level too.
Consider this snippet of an
0.1.0/manifest.ymlexample:If my data stream(s) don't have a
streamskey, the generated policy will just have aninputwithstreams: [], and the variablehostwill not be there even if I had filled it in the UI.For apm-server we don't have streams, so we need that the
varsdefined at the policy level get picked up and rendered in the generated policy.Not sure on which repo this issue belongs, let me know if it should be transferred to Kibana.
Update: The ideal way forward is that the top level config shows right under
inputs, and not under astreamsentry. For this we need hbs templates at the top level too.