mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
Fixed broken cross doc links.
This commit is contained in:
parent
e573fdec52
commit
9af81086f6
4 changed files with 12 additions and 12 deletions
|
@ -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/shield-2.0
|
||||
:k4pull: https://github.com/elastic/kibana/pull/
|
||||
|
||||
include::introduction.asciidoc[]
|
||||
|
|
|
@ -33,7 +33,7 @@ That's it! Kibana is now running on port 5601.
|
|||
[float]
|
||||
[[kibana-dynamic-mapping]]
|
||||
==== Kibana and Elasticsearch Dynamic Mapping
|
||||
By default, Elasticsearch enables {ref}mapping-dynamic-mapping.html[dynamic mapping] for fields. Kibana needs dynamic mapping
|
||||
By default, Elasticsearch enables {ref}dynamic-mapping.html[dynamic mapping] for fields. Kibana needs dynamic mapping
|
||||
to use fields in visualizations correctly, as well as to manage the `.kibana` index where saved searches,
|
||||
visualizations, and dashboards are stored.
|
||||
|
||||
|
|
|
@ -9,7 +9,7 @@ data source types:
|
|||
* A saved search
|
||||
* An existing saved visualization
|
||||
|
||||
Visualizations are based on the {ref}/search-aggregations.html[aggregation] feature introduced in Elasticsearch 1.x.
|
||||
Visualizations are based on the {ref}search-aggregations.html[aggregation] feature introduced in Elasticsearch 1.x.
|
||||
|
||||
[float]
|
||||
[[createvis]]
|
||||
|
@ -89,9 +89,9 @@ the current visualization.
|
|||
[[aggregation-builder]]
|
||||
===== Aggregation Builder
|
||||
|
||||
Use the aggregation builder on the left of the page to configure the {ref}/search-aggregations.html#_metrics_aggregations[metric] and {ref}/search-aggregations.html#_bucket_aggregations[bucket] aggregations used in your
|
||||
Use the aggregation builder on the left of the page to configure the {ref}search-aggregations-metrics.html[metric] and {ref}search-aggregations-bucket.html[bucket] aggregations used in your
|
||||
visualization. Buckets are analogous to SQL `GROUP BY` statements. For more information on aggregations, see the main
|
||||
{ref}/search-aggregations.html[Elasticsearch aggregations reference].
|
||||
{ref}search-aggregations.html[Elasticsearch aggregations reference].
|
||||
|
||||
Bar, line, or area chart visualizations use _metrics_ for the y-axis and _buckets_ are used for the x-axis, segment bar
|
||||
colors, and row/column splits. For pie charts, use the metric for the slice size and the bucket for the number of
|
||||
|
|
|
@ -4,27 +4,27 @@ chart, or for split charts.
|
|||
This chart's X axis supports the following aggregations. Click the linked name of each aggregation to visit the main
|
||||
Elasticsearch documentation for that aggregation.
|
||||
|
||||
*Date Histogram*:: A {ref}/search-aggregations-bucket-datehistogram-aggregation.html[_date histogram_] is built from a
|
||||
*Date Histogram*:: A {ref}search-aggregations-bucket-datehistogram-aggregation.html[_date histogram_] is built from a
|
||||
numeric field and organized by date. You can specify a time frame for the intervals in seconds, minutes, hours, days,
|
||||
weeks, months, or years. You can also specify a custom interval frame by selecting *Custom* as the interval and
|
||||
specifying a number and a time unit in the text field. Custom interval time units are *s* for seconds, *m* for minutes,
|
||||
*h* for hours, *d* for days, *w* for weeks, and *y* for years. Different units support different levels of precision,
|
||||
down to one second.
|
||||
|
||||
*Histogram*:: A standard {ref}/search-aggregations-bucket-histogram-aggregation.html[_histogram_] is built from a
|
||||
*Histogram*:: A standard {ref}search-aggregations-bucket-histogram-aggregation.html[_histogram_] is built from a
|
||||
numeric field. Specify an integer interval for this field. Select the *Show empty buckets* checkbox to include empty
|
||||
intervals in the histogram.
|
||||
*Range*:: With a {ref}/search-aggregations-bucket-range-aggregation.html[_range_] aggregation, you can specify ranges
|
||||
of values for a numeric field. Click *Add Range* to add a set of range endpoints. Click the red *(x)* symbol to remove
|
||||
a range.
|
||||
*Date Range*:: A {ref}/search-aggregations-bucket-daterange-aggregation.html[_date range_] aggregation reports values
|
||||
*Date Range*:: A {ref}search-aggregations-bucket-daterange-aggregation.html[_date range_] aggregation reports values
|
||||
that are within a range of dates that you specify. You can specify the ranges for the dates using
|
||||
{ref}/mapping-date-format.html#date-math[_date math_] expressions. Click *Add Range* to add a set of range endpoints.
|
||||
{ref}common-options.html#date-math[_date math_] expressions. Click *Add Range* to add a set of range endpoints.
|
||||
Click the red *(/)* symbol to remove a range.
|
||||
*IPv4 Range*:: The {ref}/search-aggregations-bucket-iprange-aggregation.html[_IPv4 range_] aggregation enables you to
|
||||
*IPv4 Range*:: The {ref}search-aggregations-bucket-iprange-aggregation.html[_IPv4 range_] aggregation enables you to
|
||||
specify ranges of IPv4 addresses. Click *Add Range* to add a set of range endpoints. Click the red *(/)* symbol to
|
||||
remove a range.
|
||||
*Terms*:: A {ref}/search-aggregations-bucket-terms-aggregation.html[_terms_] aggregation enables you to specify the top
|
||||
*Terms*:: A {ref}search-aggregations-bucket-terms-aggregation.html[_terms_] aggregation enables you to specify the top
|
||||
or bottom _n_ elements of a given field to display, ordered by count or a custom metric.
|
||||
*Filters*:: You can specify a set of {ref}/search-aggregations-bucket-filters-aggregation.html[_filters_] for the data.
|
||||
You can specify a filter as a query string or in JSON format, just as in the Discover search bar. Click *Add Filter* to
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue