Stack Management
editStack Management
editStack Management is home to UIs for managing all things Elastic Stack— indices, clusters, licenses, UI settings, index patterns, spaces, and more.
Access to individual features is governed by Elasticsearch and Kibana privileges. Consult your administrator if you do not have the appropriate access.
Ingest
editCreate and manage Elasticsearch pipelines that enable you to perform common transformations and enrichments on your data. |
|
Create, edit, and delete your Logstash pipeline configurations. |
|
Manage your Beats configurations in a central location and quickly deploy configuration changes to all Beats running across your enterprise. |
Data
editView index settings, mappings, and statistics and perform operations, such as refreshing, flushing, and clearing the cache. Practicing good index management ensures that your data is stored cost effectively. |
|
Create a policy for defining the lifecycle of an index as it ages through the hot, warm, cold, and delete phases. Such policies help you control operation costs because you can put data in different resource tiers. |
|
Define a policy that creates, schedules, and automatically deletes snapshots to ensure that you have backups of your cluster in case something goes wrong. |
|
Create a job that periodically aggregates data from one or more indices, and then rolls it into a new, compact index. Rollup indices are a good way to store months or years of historical data in combination with your raw data. |
|
Use transforms to pivot existing Elasticsearch indices into summarized or entity-centric indices. |
|
Replicate indices on a remote cluster and copy them to a follower index on a local cluster. This is important for disaster recovery. It also keeps data local for faster queries. |
|
Manage your remote clusters for use with cross-cluster search and cross-cluster replication. You can add and remove remote clusters, and check their connectivity. |
Alerts and Insights
editCentrally manage your alerts across Kibana. Create and manage reusable connectors for triggering actions. |
|
Monitor the generation of reports—PDF, PNG, and CSV—and download reports that you previously generated. A report can contain a dashboard, visualization, saved search, or Canvas workpad. |
|
View your anomaly detection jobs and data frame analytics jobs. Open the Single Metric Viewer or Anomaly Explorer to see your machine learning results. |
|
Detect changes in your data by creating, managing, and monitoring alerts. For example, you might create an alert when the maximum total CPU usage on a machine goes above a certain percentage. |
Security
editView the users that have been defined on your cluster. Add or delete users and assign roles that give users specific privileges. |
|
View the roles that exist on your cluster. Customize the actions that a user with the role can perform, on a cluster, index, and space level. |
|
Create secondary credentials so that you can send requests on behalf of the user. Secondary credentials have the same or lower access rights. |
|
Assign roles to your users using a set of rules. Role mappings are required when authenticating via an external identity provider, such as Active Directory, Kerberos, PKI, OIDC, and SAML. |
Kibana
editCreate and manage the index patterns that retrieve your data from Elasticsearch. |
|
Copy, edit, delete, import, and export your saved objects. These include dashboards, visualizations, maps, index patterns, Canvas workpads, and more. |
|
Create spaces to organize your dashboards and other saved objects into categories. A space is isolated from all other spaces, so you can tailor it to your needs without impacting others. |
|
Customize Kibana to suit your needs. Change the format for displaying dates, turn on dark mode, set the timespan for notification messages, and much more. |
Stack
editView the status of your license, start a trial, or install a new license. For the full list of features that are included in your license, see the subscription page. |
|
Identify the issues that you need to address before upgrading to the next major version of Elasticsearch, and then reindex, if needed. |