github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 17:28:26 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Updates X-Pack terminology (#28208)

Browse source
This commit is contained in:
Lisa Cawley 2019-01-08 08:48:36 -08:00 • committed by lcawl
parent a02a30a6ac
commit fc699c1d4e
11 changed files with 34 additions and 35 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/apm/index.asciidoc
View file

@ -7,7 +7,7 @@
Elastic Application Performance Monitoring (APM) automatically collects in-depth
performance metrics and errors from inside your applications.
The **APM** page in {kib} is provided with the {xpack} basic license. It
The **APM** page in {kib} is provided with the basic license. It
enables developers to drill down into the performance data for their applications
and quickly locate the performance bottlenecks.

4
docs/dev-tools/grokdebugger/index.asciidoc
View file

@ -14,8 +14,8 @@ with over 120 reusable grok patterns. See
https://github.com/elastic/elasticsearch/tree/master/modules/ingest-common/src/main/resources/patterns[Ingest node grok patterns] and https://github.com/logstash-plugins/logstash-patterns-core/tree/master/patterns[Logstash grok patterns]
for the full list of patterns.
{xpack} includes a Grok Debugger tool that you can use to build and debug
grok patterns before you use them in your data processing pipelines. Because
You can build and debug grok patterns in the Grok Debugger tool in {kib}
before you use them in your data processing pipelines. Because
ingest node and Logstash share the same grok implementation and pattern
libraries, any grok pattern that you create in the Grok Debugger will work
in ingest node and Logstash.

2
docs/dev-tools/searchprofiler/getting-started.asciidoc
View file

@ -9,7 +9,7 @@ ifdef::gs-mini[]
== Getting Started
endif::gs-mini[]
The Search Profiler is automatically enabled in {kib}. It is located under the
The {searchprofiler} is automatically enabled in {kib}. It is located under the
*Dev Tools* tab in {kib}.
[[first-profile]]

3
docs/dev-tools/searchprofiler/gs-index.asciidoc
View file

@ -1,3 +1,4 @@
[role="xpack"]
[[xpack-profiler]]
= Profiling your Queries and Aggregations
@ -7,7 +8,7 @@ Elasticsearch has a powerful profiler API which can be used to inspect and analy
your search queries. The response, however, is a very large JSON blob which is
difficult to analyze by hand.
{xpack} includes the Search Profiler tool which can transform this JSON output
The {searchprofiler} tool can transform this JSON output
into a visualization that is easy to navigate, allowing you to diagnose and debug
poorly performing queries much faster.

2
docs/dev-tools/searchprofiler/index.asciidoc
View file

@ -6,7 +6,7 @@ Elasticsearch has a powerful profiler API which can be used to inspect and analy
your search queries. The response, however, is a very large JSON blob which is
difficult to analyze by hand.
{xpack} includes the Search Profiler tool which can transform this JSON output
The {searchprofiler} tool can transform this JSON output
into a visualization that is easy to navigate, allowing you to diagnose and debug
poorly performing queries much faster.

2
docs/management.asciidoc
View file

@ -9,8 +9,6 @@ patterns, advanced settings that tweak the behaviors of Kibana itself, and
the various "objects" that you can save throughout Kibana such as searches,
visualizations, and dashboards.
This section is pluginable, so in addition to the out of the box capabilities,
packs such as {xpack} can add additional management capabilities to Kibana.
--
include::management/managing-licenses.asciidoc[]

7
docs/reporting/gs-index.asciidoc
View file

@ -1,9 +1,10 @@
[role="xpack"]
[[xpack-reporting]]
= Reporting from Kibana
[partintro]
--
{xpack} enables you to generate reports that contain {kib} dashboards,
You can generate reports that contain {kib} dashboards,
visualizations, and saved searches. The reports are exported as
print-optimized PDF documents.
@ -15,12 +16,12 @@ The following Reporting button appears in the {kib} toolbar:
image:images/reporting.jpg["Reporting",link="reporting.jpg"]
You can also {xpack-ref}/automating-report-generation.html[generate reports automatically].
You can also {stack-ov}/automating-report-generation.html[generate reports automatically].
IMPORTANT: Reports are stored in the `.reporting-*` indices. Any user with
access to these indices has access to every report generated by all users.
To use {reporting} in a production environment, {xpack-ref}/securing-reporting.html[secure
To use {reporting} in a production environment, {stack-ov}/securing-reporting.html[secure
the Reporting endpoints].
--

2
docs/reporting/index.asciidoc
View file

@ -4,7 +4,7 @@
[partintro]
--
{xpack} enables you to generate reports that contain {kib} dashboards,
You can generate reports that contain {kib} dashboards,
visualizations, and saved searches. Dashboards and visualizations are
exported as PDF documents, while saved searches in Discover
are exported to CSV.

9
docs/security/index.asciidoc
View file

@ -2,11 +2,12 @@
[[xpack-security]]
== Security
{xpack} security enables you to easily secure a cluster. With security, you can
The {stack} {security-features} enable you to easily secure a cluster. With
security, you can
password-protect your data as well as implement more advanced security measures
such as encrypting communications, role-based access control, IP filtering, and
auditing. For more information, see
{xpack-ref}/xpack-security.html[Securing {es} and {kib}] and
{stack-ov}/elasticsearch-security.html[Securing {es} and {kib}] and
<<using-kibana-with-security,Configuring Security in {kib}>>.
[float]
@ -15,7 +16,7 @@ auditing. For more information, see
You can create and manage users on the *Management* / *Security* / *Users* page.
You can also change their passwords and roles. For more information about
authentication and built-in users, see
{xpack-ref}/setting-up-authentication.html[Setting Up User Authentication].
{stack-ov}/setting-up-authentication.html[Setting up user authentication].
[float]
=== Roles
@ -25,7 +26,7 @@ You can manage roles on the *Management* / *Security* / *Roles* page, or use
{kib} see <<xpack-security-authorization, {kib} Authorization>>.
For a more holistic overview of configuring roles for the entire stack,
see {xpack-ref}/authorization.html[Configuring Role-based Access Control].
see {stack-ov}/authorization.html[Configuring role-based access control].
[NOTE]
============================================================================

18
docs/settings/ssl-settings.asciidoc
View file

@ -1,9 +1,8 @@
[float]
=== {component} TLS/SSL Settings
You can configure the following TLS/SSL settings. If the settings are not configured,
the {xpack} defaults will be used. See
{xpack-ref}/security-settings.html[Default TLS/SSL Settings].
//<<ssl-tls-settings, {xpack} defaults>> will be used.
You can configure the following TLS/SSL settings. If the settings are not
configured, the default values are used. See
{stack-ov}/security-settings.html[Default TLS/SSL Settings].
ifdef::server[]
+{ssl-prefix}.ssl.enabled+::
@ -45,9 +44,9 @@ Java Cryptography Architecture documentation]. Defaults to the value of
The following settings are used to specify a private key, certificate, and the
trusted certificates that should be used when communicating over an SSL/TLS connection.
If none of the settings below are specified, this will default to the {xpack} defaults.
See {xpack-ref}/security-settings.html[Default TLS/SSL Settings].
//<<ssl-tls-settings, {xpack} defaults>>.
If none of the settings below are specified, the default values are used.
See {stack-ov}/security-settings.html[Default TLS/SSL settings].
ifdef::server[]
A private key and certificate must be configured.
endif::server[]
@ -55,9 +54,8 @@ ifndef::server[]
A private key and certificate are optional and would be used if the server requires client authentication for PKI
authentication.
endif::server[]
If none of the settings below are specified, the {xpack} defaults will be used.
See {xpack-ref}/security-settings.html[Default TLS/SSL Settings].
//<<ssl-tls-settings, {xpack} defaults>> will be used.
If none of the settings below are specified, the defaults values are used.
See {stack-ov}/security-settings.html[Default TLS/SSL settings].
[float]
===== PEM Encoded Files

18
docs/setup/production.asciidoc
View file

@ -1,9 +1,9 @@
[[production]]
== Using Kibana in a production environment
* <<configuring-kibana-shield, Using Kibana with {xpack}>>
* <<enabling-ssl, Enabling SSL>>
* <<load-balancing, Load balancing across multiple {es} nodes>>
* <<configuring-kibana-shield>>
* <<enabling-ssl>>
* <<load-balancing>>
How you deploy Kibana largely depends on your use case. If you are the only user,
you can run Kibana on your local machine and configure it to point to whatever
@ -19,19 +19,19 @@ and an Elasticsearch client node on the same machine. For more information, see
[float]
[[configuring-kibana-shield]]
=== Using Kibana with {security}
=== Using {stack} {security-features}
You can use {stack-ov}/xpack-security.html[{security}] to control what
Elasticsearch data users can access through Kibana.
You can use {stack-ov}/elasticsearch-security.html[{stack} {security-features}]
to control what {es} data users can access through Kibana.
When {security} is enabled, Kibana users have to log in. They need to
When {security-features} are enabled, Kibana users have to log in. They need to
have the `kibana_user` role as well as access to the indices they
will be working with in Kibana.
If a user loads a Kibana dashboard that accesses data in an index that they
are not authorized to view, they get an error that indicates the index does
not exist. {security} does not currently provide a way to control which
users can load which dashboards.
not exist. The {security-features} do not currently provide a way to control
which users can load which dashboards.
For information about setting up Kibana users, see
{kibana-ref}/using-kibana-with-security.html[Configuring security in Kibana].