[Fleet] Test ticket for: Allow to preconfigure (same cluster) alternative ES outputs

[EricDavisX]

What tickets / PRs do we know relate:
Kibana side: #108968 which is partially resolved by #111002
Beats / Agent repo side: ?
Fleet-Server side: TBD (need to find ticket)

Let's talk about:

• what is implemented for 7.16:
  Lorem ipsum

• what is tested with unit/system/api/e2e-tests
  Lorem ipsum

• what we want from any manual testing for now (subsequent releases are expected to build on this and we can leave that aside for now)
  Lorem ipsum

• what can we summarize for the Docs team here to collect info for the Docs to be enhanced?
  Lorem ipsum

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[EricDavisX]

resolution of this ticket will be when testing is done, and we can test when we have clear guidance / info on what is implemented and what we want to test further. @nchaulet I hope you don't mind I tagged you as 'owner' for now, we can pass it to @dikshachauhan-qasource when she knows how to test. sound ok? @jen-huang Let me know if we want to tackle this off-line or in any different way.

[nchaulet]

@EricDavisX I am currently writing an e2e test to test that.
Currently what is implemented:

• You can define alternative ES outputs (on the same ES cluster) in the kibana config file
• You can use these in the preconfigured policies (kibana config file too)

[nchaulet]

I think we can close that one as testing have been implemented here elastic/e2e-testing#1680