[Agent] Index, template, ILM setup strategy for the Agent.

[elasticmachine]

Original comment by @ph:

As discussed in LINK REDACTED

We look more into option 5.

Manual install in the UI

• Beats don’t install templates or ILM policies
• Agent don’t install templates of ILM policies
• Agent does a check to make sure we can send data to ES cluster with the defined index or alias, the check is done on every INPUTs, the Agent filter inputs that pass the checks.
  • Checks:
  • Check write alias first, if it exist the input is OK.
  • Check for index patterns match, if it we have a match the input is OK.
  • If a pipeline is defined and the pipeline exist the inputs is OK
  • If nothing on the above is set the user goes to the Kibana integrations manager UI and click install templates and create alias / ILM policy.
• Beats can now send data.

[elasticmachine]

Original comment by @ph:

cc @ruflin @urso

[michalpristas]

@ph still valid?

[ph]

lets close this, this is replaced by the issues you created today.