[Security Solution] Inconsistent spellings used for Elasticsearch under Administration tab

[muskangulati-qasource]

Describe the bug
Inconsistent spellings used for Elasticsearch under Administration tab

Build Details:

Platform: Staging
Version: 7.10.2-SNAPSHOT
Commit: 733d0aa29750868a043ec307f27a0506d9a3ed62
Build number: 36123
Artifact: https://artifacts-api.elastic.co/v1/search/7.10.2-SNAPSHOT

Browser Details
All

Preconditions

1. Cloud environment on staging should exist.
2. Endpoint should be deployed with Security Integration installed.

Steps to Reproduce

1. Navigate to Kibana URL on Browser.
2. Click on the "Administration" tab under Security from the left navigation bar.
3. Click on the 'Success' hyperlink under the policy status.
4. Observe that under the Streaming section, Elasticsearch is spelt differently for different logs

Test data
N/A

Impacted Test case(s)
N/A

Actual Result
Inconsistent spellings used for Elasticsearch under Administration tab

Expected Result
Same spellings should be used for Elasticsearch.

What's Working
N/A

What's not Working
N/A

Screenshots

Logs
N/A

[muskangulati-qasource]

@manishgupta-qasource please review!

[manishgupta-qasource]

Reviewed & Assigned to @kevinlog

[muskangulati-qasource]

Hi @kevinlog,

We have validated this ticket on 7.11.0 BC2 and found that issue is fixed.

Build Details:

Platform: Staging
Version: 7.11.0-BC2
Commit: a5126f7a280a6f4a27dc3aca65c1c89ccd1ac694
Build number: 37605

Refer Screenshot

Hence, marking this ticket as 'Validated'.

Thanks!!