WARNING: Version 6.0 of Kibana has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
X-Pack Breaking changes in 6.0
editX-Pack Breaking changes in 6.0
editThis section summarizes the changes that you need to be aware of when migrating your application to X-Pack 6.0.
- Reporting
-
- When X-Pack security is enabled, reports will only be accessible to the user that created them.
-
When X-Pack security is enabled, user authorization is controlled by the
xpack.reporting.roles.allowsetting in thekibana.ymlwhich defaults to['reporting_user']. Users will no longer have access to the underlying X-Pack reporting indices in Elasticsearch when assigned to the built-inreporting_userrole. If using custom reporting roles, the privileges to the indices will need to be removed, and the role will need to be added to thexpack-reporting.roles.allowsetting.
- Watcher
-
-
The watch
_statusfield has been renamed tostatus, as underscores in field names will not be allowed. - The built-in HTTP client used in webhooks, the http input and the http email attachment has been replaced. This results in the need to always escape all parts of an URL.
- The new built-in HTTP client also enforces a maximum request size, which defaults to 10mb.
-
The watch