"Elasticsearch URL" field is not displayed under Overview section on Fleet->Agent Details page

[ghost]

Kibana version:
Kibana: 8.0.0-SNAPSHOT Kibana cloud environment

Elasticsearch version:
Elasticsearch: 8.0.0-SNAPSHOT cloud environment

Host OS and Browser version:
Windows x64, All

Original install method (e.g. download page, yum, from source, etc.):
8.0.0-SNAPSHOT Kibana cloud environment from https://staging.found.no

Description
"Elasticsearch URL" field is not displayed under Overview section on Fleet->Agent Details page

Preconditions

1. 8.0.0-SNAPSHOT Kibana cloud environment(with commit 818246e) should be available.
2. Login into the above Kibana environment with 'elastic' superuser.
3. 8.0.0-SNAPSHOT version windows-x86_64.zip agent should be installed with Default policy on above kibana :-
   Agent download location: https://snapshots.elastic.co/8.0.0-850b25f2/downloads/beats/elastic-agent/elastic-agent-8.0.0-SNAPSHOT-windows-x86_64.zip

Steps to Reproduce

1. Open the left hand menu and click 'Fleet' link under Management.
2. Navigate to Agents tab in Kibana.
3. Click on prerequisite host and navigate to Agent Details page.
4. Observe that "Elasticsearch URL" field is not displayed under Overview section.

Test data
N/A

Impacted Test case id
N/A

Actual Result
"Elasticsearch URL" field is not displayed under Overview section on Fleet->Agent Details page

Expected Result
"Elasticsearch URL" field and corresponding value from Fleet's "global output" settings should be displayed under Overview section on Fleet->Agent Details page(as per #81872_comment)

What's working

• All other fields are displayed under Overview section on Fleet->Agent Details page.

What's not working

• N/A

Screenshot

Logs
N/A

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[ghost]

@manishgupta-qasource Please review the bug

[manishgupta-qasource]

Reviewed & assigned to @EricDavisX

[EricDavisX]

@nchaulet @hbharding hi - Nicolas and Henry, did we decide not to put that part of the design in for 7.11? Please assess and put the correct impact on it and we can choose if we want to do anything for 7.11 at this point or just for 7.12 or wait for a further design effort. Thank you.

[nchaulet]

I missed that field during the implementation, let me now if we should correct it as a bug or if it's okay if the field is not here.

[EricDavisX]

@ph @mostlyjason @hbharding is it needed? That field is expected to change infrequently, it may not be needed. I don't feel strongly that it is worth extra changes, at least not without knowing more of the user value.

[ph]

Close for now, we only have a single ES output.

[EricDavisX]

@rahulgupta-qasource confirming - can you update the test content that may relate to this please? It is an accepted change from the design, it won't be fixed or thought about more until we have multiple inputs if / when later on.

[ghost]

Hi @EricDavisX

Thank you for sharing the feedback.

We have updated the corresponding testcase https://elastic.testrail.io/index.php?/cases/view/35178 accordingly.