Grant privileges and roles needed to read Heartbeat data from Kibana
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Kibana users typically need to view dashboards and visualizations that contain Heartbeat data. These users might also need to create and edit dashboards and visualizations.
To grant users the required privileges:
Create a reader role, called something like
heartbeat_reader, that has the following privilege:Type Privilege Purpose Index readonheartbeat-*indicesRead data indexed by Heartbeat Spaces ReadorAllon Dashboards, Visualize, and DiscoverAllow the user to view, edit, and create dashboards, as well as browse data. Spaces ReadorAllon Kibana UptimeAllow the use of Kibana Uptime Assign the reader role, along with the following built-in roles, to users who need to read Heartbeat data:
Role Purpose monitoring_userAllow users to monitor the health of Heartbeat itself. Only assign this role to users who manage Heartbeat.