9bc4d9158b
* [status] Only provide latest metrics * [status] Snake case requests object * [status] Add build snapshot flag, last updated time * [status] Re-add requests per second * [status] Add uptime * [status] collection_time -> collection_interval, add memory object * [status] Add api tests * [status] Add breaking changes docs * [status] Remove metrics config * [status] nest load under cpu, shorten memory and average * [status] collection_time -> collection_interval * [status api] Unnest heap, rename load to load average
23 lines
No EOL
971 B
Text
23 lines
No EOL
971 B
Text
[[breaking-changes-6.0]]
|
|
== Breaking changes in 6.0
|
|
|
|
This section discusses the changes that you need to be aware of when migrating
|
|
your application to Kibana 6.0.
|
|
|
|
[float]
|
|
=== Removed option to use unsupported scripting languages
|
|
*Details:* Kibana 5.x allowed users to create scripted fields using any scripting language enabled in Elasticsearch.
|
|
Kibana 6.0 will only support Painless and Lucene expression based scripts.
|
|
|
|
|
|
*Impact:* You will need to migrate your groovy, python, javascript, etc. scripted fields to Painless or Lucene expressions.
|
|
|
|
[float]
|
|
=== Changed response format of status API
|
|
*Details:* In an effort to align with our style guidelines and provide a digestible response,
|
|
the status API has changed:
|
|
|
|
* Properties are now snake cased and several have been renamed
|
|
* Metrics now provide the latest available data instead of samples over time
|
|
|
|
*Impact:* You will need to update anything using the status API and expecting the previous response format. |