[Fleet]: User is able to select output for integrations as Remote Elasticsearch under Agent policy settings.

[amolnater-qasource]

Kibana Build details:

VERSION: 8.12.0 BC3
BUILD: 69985
COMMIT: 2a8afed8572a4c709aa1c64216748197eeb9b18f
Artifact Link: https://staging.elastic.co/8.12.0-61156bc6/summary-8.12.0.html

Host OS: All

Preconditions:

1. 8.12.0 BC3 Kibana cloud environment should be available.
2. Remote Elasticsearch should be added.

Steps to reproduce:

1. Navigate to Agent Policy settings
2. Select output for integrations: Remote Elasticsearch.
3. Observe user is successfully able to save the settings and output for integrations gets set to Remote Elasticsearch in the agent policy.

Screen Recording:

Agent.policies.-.Fleet.-.Elastic.-.Google.Chrome.2023-12-27.16-04-21.mp4

Expected Result:
User should not be able to select output for integrations as Remote Elasticsearch under Agent policy settings.

Similar issue:
#173984

Feature:
#104986

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Secondary review for this ticket is Done

[nchaulet]

Hi @amolnater-qasource I think this is expected, there is no restrictions to not allow remote ES to be used for integration data, the only restriction related to remote ES is it cannot be used for some integration like fleet-server synthetics we should probably review the test case here.

[amolnater-qasource]

Hi @nchaulet

Thank you for looking into this issue.

As per the feature ticket description #104986 (comment)

“Make this output the default for agent integrations.” should be removed as remote ES does not support integration data
Do not allow remote elasticsearch output to be selected as integrations data output (should not be shown in dropdown)

The functionality was also working like this on the Snapshot build we tested during test cases creation.

Could you please confirm if any changes are made in this area under any PR, so that we can update the testcases accordingly with the reference.

Please let us know if we are missing anything here.

Thanks!

[nchaulet]

@amolnater-qasource this the PR that changed that feature #173353

[amolnater-qasource]

Thank you for sharing the reference PR.

We will update the test cases as per the requirements.

Hence, we are closing this issue.

[harshitgupta-qasource]

Bug Conversion

• Test-Case not required as this particular checkpoint is already covered in the following testcase:
  • https://elastic.testrail.io/index.php?/cases/view/271332

Thanks!