[Fleet]: Log level updated under Agent policy is not updated under Agent details tab.

[amolnater-qasource]

Kibana Build details:

VERSION: 8.15.0 SNAPSHOT
BUILD: 75123
COMMIT: 6e3b14fa19be367e2c29c32b56399729be3260bf

Preconditions:

1. 8.15.0-SNAPSHOT Kibana cloud environment should be available.
2. An agent should be installed and no change to logging level should be made.

Steps to reproduce:

1. Navigate to Agent policies.
2. Setting logging level to debug.
3. Navigate to View Agent policy and observe debug log level is now set.
4. Navigate to Agent details tab and observe logging level: info.
5. Observe new logs of Debug level are generated.

Expected Result:
Log level updated under Agent policy should be automatically updated under Agent details tab to clear the user which log level is actually being used.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2024-06-07.14-58-48.mp4

Feature:
#158861

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Secondary review for this ticket is Done

[jen-huang]

This one is also due to the bug elastic/elastic-agent#4747. Elastic Agent is reporting its log level incorrectly. Closing as duplicate. @amolnater-qasource please validate this scenario when that bug is fixed. Thanks :)

[amolnater-qasource]

Hi @jen-huang

We have revalidated this issue on latest 8.15.0 SNAPSHOT kibana cloud environment and found it fixed now:

Observations:

• Log level updated under Agent policy is updated under Agent details tab.

Screen Recording:

Agents.-.Fleet.-.Elastic.-.Google.Chrome.2024-06-21.11-50-53.mp4

Build details:
VERSION: 8.15.0 SNAPSHOT
BUILD: 75556
COMMIT: 1e1e35b

Hence we are marking this issue as QA:Validated.

Thanks!