mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 09:48:58 -04:00
Fixed hard coded doc links
This commit is contained in:
parent
41bfcb324a
commit
e041ea48f5
5 changed files with 13 additions and 14 deletions
|
@ -195,11 +195,11 @@ yellow open logstash-2015.05.20 5 1 4750 0 16.4mb
|
|||
[[tutorial-define-index]]
|
||||
=== Defining Your Index Patterns
|
||||
|
||||
Each set of data loaded to Elasticsearch has an
|
||||
https://www.elastic.co/guide/en/kibana/current/settings.html#settings-create-pattern[index pattern]. In the previous
|
||||
section, the Shakespeare data set has an index named `shakespeare`, and the accounts
|
||||
data set has an index named `bank`. An _index pattern_ is a string with optional wildcards that can match multiple
|
||||
indices. For example, in the common logging use case, a typical index name contains the date in MM-DD-YYYY
|
||||
Each set of data loaded to Elasticsearch has an
|
||||
<<settings-create-pattern,index pattern>>. In the previous
|
||||
section, the Shakespeare data set has an index named `shakespeare`, and the accounts
|
||||
data set has an index named `bank`. An _index pattern_ is a string with optional wildcards that can match multiple
|
||||
indices. For example, in the common logging use case, a typical index name contains the date in MM-DD-YYYY
|
||||
format, and an index pattern for May would look something like `logstash-2015.05*`.
|
||||
|
||||
For this tutorial, any pattern that matches the name of an index we've loaded will work. Open a browser and
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
[[kibana-guide]]
|
||||
= Kibana User Guide
|
||||
|
||||
:ref: http://www.elastic.co/guide/en/elasticsearch/reference/current/
|
||||
:shield: https://www.elastic.co/guide/en/shield/current
|
||||
:ref: http://www.elastic.co/guide/en/elasticsearch/reference/2.0/
|
||||
:shield: https://www.elastic.co/guide/en/shield/2.0/
|
||||
:k4issue: https://github.com/elastic/kibana/issues/
|
||||
:k4pull: https://github.com/elastic/kibana/pull/
|
||||
:version: 4.2
|
||||
|
|
|
@ -14,8 +14,7 @@ Setting up Kibana is a snap. You can install Kibana and start exploring your
|
|||
Elasticsearch indices in minutes -- no code, no additional infrastructure required.
|
||||
|
||||
NOTE: This guide describes how to use Kibana 4.2. For information about what's new
|
||||
in Kibana 4.2, see the <<releasenotes, release notes>>. For earlier versions of Kibana 4, see the
|
||||
http://www.elastic.co/guide/en/kibana/4.1/index.html[Kibana 4.1 User Guide]. For information about Kibana 3, see the
|
||||
in Kibana 4.2, see the <<releasenotes, release notes>>. For information about Kibana 3, see the
|
||||
http://www.elastic.co/guide/en/kibana/3.0/index.html[Kibana 3 User Guide].
|
||||
|
||||
[float]
|
||||
|
|
|
@ -107,7 +107,7 @@ across the nodes is to run an Elasticsearch _client_ node on the same machine as
|
|||
Elasticsearch client nodes are essentially smart load balancers that are part of the cluster. They
|
||||
process incoming HTTP requests, redirect operations to the other nodes in the cluster as needed, and
|
||||
gather and return the results. For more information, see
|
||||
http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html[Node] in the Elasticsearch reference.
|
||||
{ref}/modules-node.html[Node] in the Elasticsearch reference.
|
||||
|
||||
To use a local client node to load balance Kibana requests:
|
||||
|
||||
|
|
|
@ -204,8 +204,8 @@ WARNING: Computing data on the fly with scripted fields can be very resource int
|
|||
Kibana's performance. Keep in mind that there's no built-in validation of a scripted field. If your scripts are
|
||||
buggy, you'll get exceptions whenever you try to view the dynamically generated data.
|
||||
|
||||
Scripted fields use the Lucene expression syntax. For more information,
|
||||
see http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-scripting.html#_lucene_expressions_scripts[
|
||||
Scripted fields use the Lucene expression syntax. For more information,
|
||||
see {ref}/modules-scripting.html#_lucene_expressions_scripts[
|
||||
Lucene Expressions Scripts].
|
||||
|
||||
You can reference any single value numeric field in your expressions, for example:
|
||||
|
@ -224,8 +224,8 @@ To create a scripted field:
|
|||
. Enter the expression that you want to use to compute a value on the fly from your index data.
|
||||
. Click *Save Scripted Field*.
|
||||
|
||||
For more information about scripted fields in Elasticsearch, see
|
||||
http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-scripting.html[Scripting].
|
||||
For more information about scripted fields in Elasticsearch, see
|
||||
{ref}/modules-scripting.html[Scripting].
|
||||
|
||||
NOTE: In Elasticsearch releases 1.4.3 and later, this functionality requires you to enable
|
||||
{ref}/modules-scripting.html[dynamic Groovy scripting].
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue