The alerting framework currently does not allow alert creation if ES security is enabled but TLS between ES and Kibana is disabled (meaning API keys cannot be created). In this scenario, when a user tries to go to the Rules & Connector UI, they receive a warning message that prevents them from creating rules. However, if a user tries to create stack monitoring rules, they receive a 500 error toaster. It might be nice for stack monitoring to handle this case before user gets to the 500 errors.
The alerting framework currently does not allow alert creation if ES security is enabled but TLS between ES and Kibana is disabled (meaning API keys cannot be created). In this scenario, when a user tries to go to the Rules & Connector UI, they receive a warning message that prevents them from creating rules. However, if a user tries to create stack monitoring rules, they receive a 500 error toaster. It might be nice for stack monitoring to handle this case before user gets to the 500 errors.
Alerting offers an API (https://www.elastic.co/guide/en/kibana/master/get-alerting-framework-health-api.html) to check the health of the framework. If either
is_sufficiently_secure
orhas_permanent_encryption_key
isfalse
, rules will not be able to be created.