- Kibana Guide: other versions:
- What is Kibana?
- What’s new in 8.3
- Kibana concepts
- Quick start
- Set up
- Install Kibana
- Configure Kibana
- Alerting and action settings
- APM settings
- Banners settings
- Enterprise Search settings
- Fleet settings
- i18n settings
- Logging settings
- Logs settings
- Metrics settings
- Monitoring settings
- Reporting settings
- Search sessions settings
- Secure settings
- Security settings
- Spaces settings
- Task Manager settings
- Telemetry settings
- URL drilldown settings
- Start and stop Kibana
- Access Kibana
- Securing access to Kibana
- Add data
- Upgrade Kibana
- Configure security
- Configure reporting
- Configure logging
- Configure monitoring
- Command line tools
- Production considerations
- Discover
- Dashboard and visualizations
- Canvas
- Maps
- Build a map to compare metrics by country or region
- Track, visualize, and alert on assets in real time
- Map custom regions with reverse geocoding
- Heat map layer
- Tile layer
- Vector layer
- Plot big data
- Search geographic data
- Configure map settings
- Connect to Elastic Maps Service
- Import geospatial data
- Troubleshoot
- Reporting and sharing
- Machine learning
- Graph
- Alerting
- Observability
- APM
- Security
- Dev Tools
- Fleet
- Osquery
- Stack Monitoring
- Stack Management
- REST API
- Get features API
- Kibana spaces APIs
- Kibana role management APIs
- User session management APIs
- Saved objects APIs
- Data views API
- Index patterns APIs
- Alerting APIs
- Action and connector APIs
- Cases APIs
- Import and export dashboard APIs
- Logstash configuration management APIs
- Machine learning APIs
- Short URLs APIs
- Get Task Manager health
- Upgrade assistant APIs
- Kibana plugins
- Troubleshooting
- Accessibility
- Release notes
- Developer guide
Kibana 8.3.3
editKibana 8.3.3
editReview the following information about the Kibana 8.3.3 release.
Known issues
editIf you have alerting rules that have been snoozed, do not upgrade Kibana from 8.3.3 to 8.4.0. Upgrade to 8.4.1 instead.
To determine if you have snoozed alerting rules, open the main menu, then click Stack Management → Rules and Connectors. Filter the rule list by selecting View → Snoozed. If you must upgrade to 8.4.0, for each space, cancel the snooze for all affected rules before you upgrade.
To identify snoozed rules in all Spaces using Dev Tools, run the following query:
GET /.kibana/_search { "query": { "exists": { "field": "alert.isSnoozedUntil" } } }
If you upgraded Kibana from 8.3.3 to 8.4.0 and you had alerting rules configured to snooze notifications, you will receive the following error message:
FATAL Error: Unable to complete saved object migrations for the [.kibana] index.
To fix that problem, restore your previous version, then upgrade to 8.4.1 instead.
Breaking change
editBreaking 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.3.
To review the breaking changes in previous versions, refer to the following:
8.2.0 | 8.1.0 | 8.0.0 | 8.0.0-rc2 | 8.0.0-rc1 | 8.0.0-beta1 | 8.0.0-alpha2 | 8.0.0-alpha1
Bug fixes
edit- Dashboard
- Discover
- Fixes filter in / filter out buttons for empty values #135919
- Elastic Security
- For the Elastic Security 8.3.3 release information, refer to Elastic Security Solution Release Notes.
- Fleet
- Lens & Visualizations
- Fixes normalizeTable performance bottleneck in Lens #135792
On this page