IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Elasticsearch Hadoop breaking changes Logstash breaking changes »

› ›

Kibana breaking changes

edit

Kibana breaking changes

edit

This list summarizes the most important breaking changes in Kibana 7.14.2. For the complete list, go to Kibana breaking changes.

Changes audit event terminology

Details
The terminology has changed for audit events logged by the alerting framework’s rules client when CRUD operations are performed.

The following audit actions are renamed:

alert_create is now rule_create
alert_get is now rule_get
alert_update is now rule_update
alert_update_api_key is now rule_update_api_key
alert_enable is now rule_enable
alert_disable is now rule_disable
alert_delete is now rule_delete
alert_find is now rule_find
alert_mute is now rule_mute
alert_unmute is now rule_unmute
alert_instance_mute is now rule_alert_mute
alert_instance_unmute is now rule_alert_unmute

The terminology in the audit messages now references rules instead of alerts. For example, User is creating alert [id=${ruleId}] is now User is creating rule [id=${ruleId}].

For more information, refer to #102263.

Impact
When you upgrade to 7.14.0, Kibana automatically uses the new terminology. No action is needed.

Refactors alerts authorization client

Details
The alerts authorization client has been refactored to be more generic. Kibana uses the existing alerting feature privilege model to provide all and read privileges to rules and alerts.

For more information, refer to #99078.

Impact
When you upgrade to 7.14.0, Kibana automatically reflects the changes. No action is needed.

« Elasticsearch Hadoop breaking changes Logstash breaking changes »