- Kibana Guide: other versions:
- What is Kibana?
- What’s new in 7.16
- Kibana concepts
- Quick start
- Set up
- Install Kibana
- Configure Kibana
- Alerting and action settings
- APM settings
- Banners settings
- Development tools settings
- Graph settings
- Fleet settings
- i18n settings
- Logging settings
- Logs settings
- Metrics settings
- Machine learning settings
- Monitoring settings
- Reporting settings
- Secure settings
- Search sessions 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 monitoring
- 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
- Index patterns APIs
- Alerting APIs
- Action and connector 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
- Accessibility
- Release notes
- Developer guide
Plugin API changes in 7.16
editPlugin API changes in 7.16
editThis page discusses the plugin API changes that you need to be aware of when migrating your application to Kibana 7.16.
Other versions: 7.15 | 7.14 | 7.13 | 7.12 | 7.11 | 7.10 | 7.9 | 7.8
Deprecation warnings logged for plugins that cannot be disabled
The ability for most plugins to be disabled using the {plugin_name}.enabled
config option has been deprecated. In 8.0, most Kibana plugins can no longer
be disabled using this option.
You can still opt-in to this feature by explicitly adding an
enabled property to your config schema. However, we recommend against
this when possible. This change affects whether or not a plugin’s code is loaded by
Kibana’s core, introducing complexity and creating a new set of configuration
scenarios that must be tested.
To allow some aspects of your plugin to be disabled,
for example the ability to remove it from the Kibana UI,
we recommend creating "nested" configuration options. For example, use
{plugin_name}.ui.enabled instead of {plugin_name}.enabled, and then read
from the configuration at runtime to conditionally render your application.
This gives you similar functionality without preventing your plugin code from loading altogether.
Refer to #112602.
Angular removed from doc viewer
You can no longer use the directive property when registering a DocView via
the addDocView() method in Discover to register an Angular doc view.
Going forward, we no longer support Angular in our plugin APIs.
Refer to #109368.
LegacyRequest type removed from Core API
The Core API no longer accepts LegacyRequest in BasePath and ScopeableRequet types.
Refer to #109243.
Legacy Elasticsearch client removed
The legacy Elasticsearch client is no longer available in CoreSetup and
RequestHandlerContext interfaces. Use the
new client
instead.
Refer to #107619.