Alert - Action: Saving to server Log - resetting level

[Rnxxx]

Kibana version: 7.10.0

Elasticsearch version: 7.10.0

Server OS version: Elastic-Cloud

Browser version: Firefox 77

Browser OS version: Windows

Original install method (e.g. download page, yum, from source, etc.): Elastic-Cloud

Description of the problem including expected versus actual behavior: In Kibana Alerts - monitoring to server log - loglevel is reset to "INFO" every time the settings are open
Resetting this option to always default "info" level is confusing. Although after saving system works as expected, while editing other settings such us threshold level, this option must be always edited or been watched for proper value before saving the Alert. There is no way to check if this setting is set to Error, Trace or any other option while checking an Alert.

Steps to reproduce:

1. Open Kibana - Stack Management - Alerts
2. Create ANY alert with Actions pointing to "Logging to Server Log", click save.
3. Open newly created Alert and click Edit
4. In righ panel, change in Actions section field "Level" to any other setting than "Info" (ie Trace, Error...)
5. Click save
6. Edit the Alert again
7. in the right panel, in Action section appears "Info" loglevel

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Describe the feature:

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[mikecote]

Hi @Rnxxx,

Thank you for raising this issue. I believe this is similar to #82341? If so, we have a fix that will be part of the 7.11 release (#83651) and we should be good to close this issue.

I am checking if we can make this part of 7.10.2 as well.

[mikecote]

Closing in favour of #82341.