Review the following information about the Kibana 8.3.1 release.
URL arguments cause API requests in Dev Tools to fail
When you add any URL arguments, such as
?pretty, to API requests, the requests fail #133965
The known issue only impacts Kibana Dev Tools. All other sources of API requests are unaffected, such as curl and Elastic Cloud API console.
Alerting rules stop running when you upgrade to 8.3.0 or 8.3.1
In 8.3.0 and 8.3.1, there is a known issue where alerting rules that were created or edited in 8.2.0 stop running when you upgrade Kibana. When you upgrade to 8.3.0 or 8.3.1, and your alerting rules have stopped running, the following error appears:
<rule-type>:<UUID>: execution failed - security_exception: [security_exception] Reason: missing authentication credentials for REST request [/_security/user/_has_privileges], caused by: ""
If you have upgraded to 8.3.0 or 8.3.1, and your alerting rules fail, reset the rules by disabling, then re-enabling them. When you disable, then re-enable your alerting rules, Kibana generates a new API key using the credentials of the user that manages the rules.
To disable, then re-enable your alerting rules:
- Open the main menu, then click Stack Management > Rules and Connectors.
- Select the failed alerting rules.
- Click Manage rules > Disable, then click Manage rules > Enable.
For more details about API key authorization, refer to Authorization.
Breaking changes can prevent your application from optimal operation and performance. Before you upgrade, review the breaking change, then mitigate the impact to your application.
There are no breaking changes in Kibana 8.3.1.
To review the breaking changes in previous versions, refer to the following:
- Adds EsArchiver datastream support #132853
- Prevent negative snooze intervals #134935
- Elastic Security
- For the Elastic Security 8.3.1 release information, refer to Elastic Security Solution Release Notes.
- Query persistent queue size for metricbeat documents #134569
- Fixes an issue where importing/copying the same saved object to the same space multiple times using the "Check for existing objects" option could fail or cause duplicates to be created #135358
- Fixes a bug where Elasticsearch nodes that stopped, then started again, were unreachable by Kibana for a given amount of requests when Kibana was configured to connect to multiple Elasticsearch nodes #134628