- 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
Update data view API
editUpdate data view API
edit[preview] This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Update part of an data view. Only the specified fields are updated in the data view. Unspecified fields stay as they are persisted.
Request
editPOST <kibana host>:<port>/api/data_views/data_view/<id>
POST <kibana host>:<port>/s/<space_id>/api/data_views/data_view/<id>
Path parameters
edit-
space_id
-
(Optional, string) An identifier for the space. If
space_id
is not provided in the URL, the default space is used. -
id
- (Required, string) The ID of the data view you want to update.
Request body
edit-
refresh_fields
-
(Optional, boolean) Reloads the data view fields after
the data view is updated. The default is
false
. -
data_view
-
(Required, object) The data view fields you want to update.
You can partially update the following fields:
-
title
-
timeFieldName
-
fields
-
sourceFilters
-
fieldFormatMap
-
type
-
typeMeta
-
Response code
edit-
200
- Indicates a successful call.
Examples
editUpdate a title of the <my-view>
data view:
$ curl -X POST api/data_views/data_view/my-view { "data_view": { "title": "some-other-view-*" } }
Customize the update behavior:
$ curl -X POST api/data_views/data_view/my-view { "refresh_fields": true, "data_view": { "fields": {} } }
All update fields are optional, but you can specify the following fields:
$ curl -X POST api/data_views/data_view/my-view { "data_view": { "title": "...", "timeFieldName": "...", "sourceFilters": [], "fieldFormats": {}, "type": "...", "typeMeta": {}, "fields": {}, "runtimeFieldMap": {} } }
The API returns the updated data view object:
{ "data_view": { } }