Describe the bug
After changing agent logging level using Fleet UI, cloudbeat failing to increase log level.
The following message appears in the agent's log:
[elastic_agent][error] cloudbeat stderr: "failed to IncreaseLevel: invalid increase level, as level \"info\" is allowed by increased level, but not by existing core\n"
Preconditions
ELK stack is deployed
Vanilla kubernetes cluster is deployed
Elastic fleet managed agent is deployed and connected
To Reproduce
Steps to reproduce the behavior:
- Navigate to Fleet UI
- Select connected agent
- Select logs tab
- Change agent's logging level to warning for example
- Apply changes
Expected behavior
Cloudbeat changes notification level and notifies that logging level is changed.
Desktop (please complete the following information):
- OS: MacOS
- Browser: Chrome
- Kibana Version: 8.5-BC1
- Endpoint Version: 8.5-BC1
Describe the bug
After changing agent logging level using Fleet UI, cloudbeat failing to increase log level.
The following message appears in the agent's log:
[elastic_agent][error] cloudbeat stderr: "failed to IncreaseLevel: invalid increase level, as level \"info\" is allowed by increased level, but not by existing core\n"Preconditions
ELK stack is deployed
Vanilla kubernetes cluster is deployed
Elastic fleet managed agent is deployed and connected
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Cloudbeat changes notification level and notifies that logging level is changed.
Desktop (please complete the following information):