[Alerts] Server log action: log level cannot be set

[Matt-Yorkley]

Kibana version:

7.9.2 (also tried in 7.9.3)

Elasticsearch version:

7.9.2 (also tried in 7.9.3)

Server OS version:

Ubuntu 18.04

Browser version:

Firefox 82.0

Browser OS version:

Ubuntu 20.04

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

apt

Describe the bug:

When setting up an alert and using the "Server log" action, the log level option does not work. There is a list of possible options, but when changing and saving it, the action always reverts to the default "info" level and is not saved.

Steps to reproduce:

1. In Kibana go to Stack Management -> Alerts
2. Create a new Alert and set the action type to "Server log"
3. Under the settings, select a non-default log level, eg: "warning"
4. Save the Alert
5. Check the alert settings again; the log level has reverted to "info"

Expected behavior:

The log level option can be set as expected.

Screenshots (if relevant):

Errors in browser console (if relevant):

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

Any additional context:

Tested in 7.9.2 and 7.9.3

Especially annoying when using the logging.quiet: true config option, as it means all "System log" alerts vanish.

[elasticmachine]

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

[pmuellr]

Thanks for the bug report @Matt-Yorkley !

It looks like - at least on master - that this is a UI issue, in that the alerting form always displays Info for the log level, despite what it's actually set to.

I was able to change it from Info to Error via the UI, and see that the log messages were now at the error level. The UI continued to display the Info level though, even across page refreshes. At GET request of the alert also showed the expected Error level being set for the action.

[Matt-Yorkley]

Ah yes, I see. It will be reset to info though if the alert is ever edited without manually re-setting the dropdown to the desired setting each time.