[Fleet]: workers written instead of worker under agent performance tuning.

[amolnater-qasource]

Kibana Build details:

VERSION: 8.12.0 BC4
BUILD: 70016
COMMIT: c2fda4713eb89786cf07dba596f6d45136858fd5

Host OS: All

Preconditions:

1. 8.12.0 BC4 Kibana cloud environment should be available.

Steps to reproduce:

1. Navigate to Fleet Settings.
2. Add Elasticsearch output> performance tuning.
3. Observe workers available instead of reserved keyword: worker.

Screenshots:

Expected Result:
worker should be written instead of workers under agent performance tuning guide as the reserved keyword is worker.

Doc link:
https://www.elastic.co/guide/en/fleet/8.12/es-output-settings.html#es-output-settings-performance-tuning-settings

Feature:
#166870

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Secondary review for this ticket is Done

[cmacknz]

Just confirming that worker is the correct word without the s: https://www.elastic.co/guide/en/beats/filebeat/current/elasticsearch-output.html#_worker

[kilfoyle]

@amolnater-qasource Since Craig confirmed above that worker is the correct term, I think the documentation page is okay.

Instead, perhaps this issue should be transferred to the Fleet team to change the UI message from workers to worker?

[amolnater-qasource]

Thank for you for the update Team.
We have updated this issue as per the requirement.

[amolnater-qasource]

Hi Team,

We have revalidated this issue on latest 8.13.0 BC5 kibana cloud environment and found it fixed now.

Observations:

• worker is written instead of workers under agent performance tuning guide as per the reserved keyword.

Screenshot:

Build details:
VERSION: 8.13.0 BC5
BUILD: 72025
COMMIT: d04713a

Hence, we are closing and marking this issue as QA:Validated.
Thanks!!