40f2784f37
While Elasticsearch ingest pipelines require a node with the `ingest` role, we don't need to include `ingest node` in the feature name. There are no official plans, but the Elasticsearch team has discussed removing the `ingest` role in the future. This also better aligns the Kibana UI with the Elasticsearch docs. The PR also makes some related changes to the Kibana docs. Relates to https://github.com/elastic/elasticsearch/pull/70253.
205 lines
6.6 KiB
Plaintext
205 lines
6.6 KiB
Plaintext
[[management]]
|
|
= Stack Management
|
|
|
|
[partintro]
|
|
--
|
|
*Stack 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 {es} and {kib} privileges.
|
|
Consult your administrator if you do not have the appropriate access.
|
|
|
|
[float]
|
|
[[manage-ingest]]
|
|
== Ingest
|
|
|
|
[cols="50, 50"]
|
|
|===
|
|
|
|
| {ref}/ingest.html[Ingest Pipelines]
|
|
| Create and manage ingest pipelines that let you perform common transformations
|
|
and enrichments on your data.
|
|
|
|
| {logstash-ref}/logstash-centralized-pipeline-management.html[Logstash Pipelines]
|
|
| Create, edit, and delete your Logstash pipeline configurations.
|
|
|
|
|
|
|===
|
|
|
|
[float]
|
|
[[manage-data]]
|
|
== Data
|
|
|
|
[cols="50, 50"]
|
|
|===
|
|
|
|
a| {ref}/index-mgmt.html[Index Management]
|
|
| View 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.
|
|
|
|
| {ref}/index-lifecycle-management.html[Index Lifecycle Policies]
|
|
|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.
|
|
|
|
| <<snapshot-repositories, Snapshot and Restore>>
|
|
|Define a policy that creates, schedules, and automatically deletes snapshots to ensure that you
|
|
have backups of your cluster in case something goes wrong.
|
|
|
|
| <<data-rollups, Rollup Jobs>>
|
|
|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.
|
|
|
|
| {ref}/transforms.html[Transforms]
|
|
|Use transforms to pivot existing {es} indices into summarized or entity-centric indices.
|
|
|
|
| {ref}/ccr-getting-started.html[Cross-Cluster Replication]
|
|
|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.
|
|
|
|
| {ref}/ccr-getting-started.html#ccr-getting-started-remote-cluster[Remote Clusters]
|
|
|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.
|
|
|===
|
|
|
|
[float]
|
|
[[manage-alerts-insights]]
|
|
== Alerts and Insights
|
|
|
|
[cols="50, 50"]
|
|
|===
|
|
|
|
| <<alerting-getting-started, Rules and Connectors>>
|
|
| Centrally <<create-and-manage-rules, manage your rules>> across {kib}. Create and <<connector-management, manage reusable
|
|
connectors>> for triggering actions.
|
|
|
|
| <<reporting-getting-started, Reporting>>
|
|
| 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.
|
|
|
|
| Machine Learning Jobs
|
|
| View, export, and import your <<xpack-ml-anomalies,{anomaly-detect}>> and
|
|
<<xpack-ml-dfanalytics,{dfanalytics}>> jobs. Open the Single Metric
|
|
Viewer or Anomaly Explorer to see your {anomaly-detect} results.
|
|
|
|
| <<watcher-ui, Watcher>>
|
|
| 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.
|
|
|
|
|===
|
|
|
|
[float]
|
|
[[manage-security]]
|
|
== Security
|
|
|
|
[cols="50, 50"]
|
|
|===
|
|
|
|
a| <<xpack-security, Users>>
|
|
|View the users that have been defined on your cluster.
|
|
Add or delete users and assign roles that give users
|
|
specific privileges.
|
|
|
|
| <<xpack-kibana-role-management, Roles>>
|
|
|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.
|
|
|
|
| <<api-keys, API Keys>>
|
|
| Create secondary credentials so that you can send requests on behalf of the user.
|
|
Secondary credentials have the same or lower access rights.
|
|
|
|
| <<role-mappings, Role Mappings>>
|
|
| 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.
|
|
|
|
|===
|
|
|
|
[float]
|
|
[[manage-kibana]]
|
|
== {kib}
|
|
|
|
[cols="50, 50"]
|
|
|===
|
|
|
|
a| <<managing-index-patterns, Manage index pattern data fields>>
|
|
|Manage the data fields in the index patterns that retrieve your data from {es}.
|
|
|
|
| <<managing-saved-objects, Saved Objects>>
|
|
| Copy, edit, delete, import, and export your saved objects.
|
|
These include dashboards, visualizations, maps, index patterns, Canvas workpads, and more.
|
|
|
|
| <<managing-tags, Tags>>
|
|
|Create, manage, and assign tags to your saved objects.
|
|
|
|
| <<search-sessions, Search Sessions>>
|
|
| Manage your saved search sessions, groups of queries that run in the background.
|
|
Search sessions are useful when your queries take longer than usual to process,
|
|
for example, when you have a large volume of data or when the performance of your storage location is slow.
|
|
|
|
|
|
| <<xpack-spaces, Spaces>>
|
|
| 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.
|
|
|
|
a| <<advanced-options, Advanced Settings>>
|
|
| Customize {kib} to suit your needs. Change the format for displaying dates, turn on dark mode,
|
|
set the timespan for notification messages, and much more.
|
|
|
|
|===
|
|
|
|
[float]
|
|
[[manage-stack]]
|
|
== Stack
|
|
|
|
[cols="50, 50"]
|
|
|===
|
|
|
|
| <<managing-licenses, License Management>>
|
|
| View 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 https://www.elastic.co/subscriptions[subscription page].
|
|
|
|
| <<upgrade-assistant, Upgrade Assistant>>
|
|
| Identify the issues that you need to address before upgrading to the
|
|
next major version of {es}, and then reindex, if needed.
|
|
|
|
|===
|
|
|
|
|
|
|
|
--
|
|
|
|
include::{kib-repo-dir}/management/advanced-options.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/management/action-types.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/management/managing-licenses.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/management/manage-index-patterns.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/management/numeral.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/management/rollups/create_and_manage_rollups.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/management/managing-saved-objects.asciidoc[]
|
|
|
|
include::security/index.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/management/snapshot-restore/index.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/spaces/index.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/management/managing-tags.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/management/upgrade-assistant/index.asciidoc[]
|
|
|
|
include::{kib-repo-dir}/management/watcher-ui/index.asciidoc[]
|