- Kibana Guide: other versions:
- Introduction
- Set Up Kibana
- Getting Started
- Discover
- Visualize
- Dashboard
- Canvas
- Graph data connections
- Machine learning
- Maps
- Infrastructure
- Logs
- APM
- Uptime
- Dev Tools
- Monitoring
- Management
- Reporting from Kibana
- REST API
- Kibana plugins
- Limitations
- Release Highlights
- Breaking Changes
- Release Notes
- Developer guide
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Use with Elasticsearch Security
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Use with Elasticsearch Security
editIf you use Elasticsearch security, you’ll need to enable certain privileges for users that would like to access the Uptime app. Below is an example of creating a user and support role to implement those privileges.
Create a role
editYou’ll need a role that lets you access the Heartbeat indices, which by default are heartbeat-*
.
You can create this with the following request:
PUT /_security/role/uptime { "indices" : [ { "names" : [ "heartbeat-*" ], "privileges" : [ "read", "view_index_metadata" ], "field_security" : { "grant" : [ "*" ] }, "allow_restricted_indices" : false } ], "applications" : [ { "application" : "kibana-.kibana", "privileges" : [ "all" ], "resources" : [ "*" ] } ], "transient_metadata" : { "enabled" : true } }
Assign the role to a user
editNext, you’ll need to create a user with both the kibana_user
, and uptime
roles.
You can do this with the following request:
PUT /_security/user/jacknich { "password" : "j@rV1s", "roles" : [ "uptime", "kibana_user" ], "full_name" : "Jack Nicholson", "email" : "jacknich@example.com", "metadata" : { "intelligence" : 7 } }
On this page
Was this helpful?
Thank you for your feedback.