Lisa Cawley
GitHub
parent
e8659817d2
commit
fcf27baef1
|
|
@ -5,8 +5,11 @@
|
|||
--
|
||||
//TBD
|
||||
|
||||
* <<xpack-graph>>
|
||||
* <<xpack-ml>>
|
||||
|
||||
--
|
||||
|
||||
include::graph/index.asciidoc[leveloffset=+1]
|
||||
|
||||
include::ml/index.asciidoc[]
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
[role="xpack"]
|
||||
[[graph-configuration]]
|
||||
== Configuring Graph
|
||||
=== Configuring Graph
|
||||
|
||||
When a user saves a graph workspace in Kibana, it is stored in the `.kibana`
|
||||
index along with other saved objects like visualizations and dashboards.
|
||||
|
|
@ -59,7 +59,7 @@ image::user/graph/images/graph-read-only-badge.png[Example of Graph's read only
|
|||
|
||||
[float]
|
||||
[[disable-drill-down]]
|
||||
=== Disabling drill down configuration
|
||||
==== Disabling drill down configuration
|
||||
|
||||
By default, users can configure _drill down_ URLs to display additional
|
||||
information about a selected vertex in a new browser window. For example,
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
[role="xpack"]
|
||||
[[graph-getting-started]]
|
||||
== Using Graph
|
||||
=== Using Graph
|
||||
|
||||
Graph is automatically enabled in {es} and {kib}.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,6 @@
|
|||
[[xpack-graph]]
|
||||
= Graphing Connections in Your Data
|
||||
== Graphing connections in your data
|
||||
|
||||
[partintro]
|
||||
--
|
||||
The {kib} {graph-features} enable you to discover how items in an
|
||||
Elasticsearch index are related. You can explore the connections between
|
||||
indexed terms and see which connections are the most meaningful. This is
|
||||
|
|
|
|||
|
|
@ -1,9 +1,7 @@
|
|||
[role="xpack"]
|
||||
[[xpack-graph]]
|
||||
= Graph data connections
|
||||
== Graph data connections
|
||||
|
||||
[partintro]
|
||||
--
|
||||
The {graph-features} enable you to discover how items in an
|
||||
Elasticsearch index are related. You can explore the connections between
|
||||
indexed terms and see which connections are the most meaningful. This can be
|
||||
|
|
@ -65,8 +63,6 @@ Advanced options let you control how your data is sampled and summarized.
|
|||
You can also set timeouts to prevent graph queries from adversely
|
||||
affecting the cluster.
|
||||
|
||||
--
|
||||
|
||||
include::getting-started.asciidoc[]
|
||||
|
||||
include::configuring-graph.asciidoc[]
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
[[graph-introduction]]
|
||||
== Introduction
|
||||
=== Introduction
|
||||
|
||||
_Graph_ provides a way to discover how items in an {es} index are related. You can
|
||||
explore the connections between indexed terms and see which connections are the most meaningful.
|
||||
|
|
@ -18,7 +18,7 @@ You can use Graph with your existing {es} indices--simply start exploring!
|
|||
|
||||
[[how-graph-works]]
|
||||
[float]
|
||||
=== How Graph Works
|
||||
==== How Graph works
|
||||
Graph provides an alternative way to extract and summarize information about the documents and terms in your {es} index. A _graph_ is really just a network of related items. In our case, this means a network of related terms in the index.
|
||||
|
||||
In the Graph API, the terms you want to include in the graph are called _vertices_.
|
||||
|
|
@ -55,7 +55,7 @@ prevent Graph queries from adversely affecting the cluster.
|
|||
|
||||
[[exploring-connections]]
|
||||
[float]
|
||||
=== Visualizing Connections with Graph
|
||||
==== Visualizing connections with Graph
|
||||
|
||||
The Graph plugin for {kib} lets you interactively explore connections within your data. This
|
||||
is a great way to get acquainted with what the Graph API has to offer.
|
||||
|
|
@ -89,13 +89,13 @@ NOTE: By default, when you submit a search query Graph searches all available fi
|
|||
|
||||
|
||||
[float]
|
||||
== Where to Go Next
|
||||
=== Where to go next
|
||||
|
||||
<<graph-getting-started, Getting Started>> :: Install the Graph plugin and Kibana app to start
|
||||
exploring relationships in your data.
|
||||
|
||||
[float]
|
||||
== Have Comments, Questions, or Feedback?
|
||||
=== Have comments, questions, or feedback?
|
||||
|
||||
Head over to our {forum}[Graph Discussion Forum] to share your experience, questions, and
|
||||
suggestions.
|
||||
|
|
|
|||
|
|
@ -1,12 +1,12 @@
|
|||
[role="xpack"]
|
||||
[[graph-limitations]]
|
||||
== Graph limitations
|
||||
=== Graph limitations
|
||||
++++
|
||||
<titleabbrev>Limitations</titleabbrev>
|
||||
++++
|
||||
|
||||
[float]
|
||||
=== Limited support for multiple indices
|
||||
==== Limited support for multiple indices
|
||||
The graph API can explore multiple indices, types, or aliases in a
|
||||
single API request, but the assumption is that each "hop" it performs
|
||||
is querying the same set of indices. Currently, it is not possible to
|
||||
|
|
|
|||
|
|
@ -1,12 +1,12 @@
|
|||
[role="xpack"]
|
||||
[[graph-troubleshooting]]
|
||||
== Graph Troubleshooting
|
||||
=== Graph Troubleshooting
|
||||
++++
|
||||
<titleabbrev>Troubleshooting</titleabbrev>
|
||||
++++
|
||||
|
||||
[float]
|
||||
=== Why are results missing?
|
||||
==== Why are results missing?
|
||||
|
||||
The default settings in Graph API requests are configured to tune out noisy
|
||||
results by using the following strategies:
|
||||
|
|
@ -30,7 +30,7 @@ of any statistical correlation with the sample.
|
|||
required to assert a relationship.
|
||||
|
||||
[float]
|
||||
=== What can I do to to improve performance?
|
||||
==== What can I do to to improve performance?
|
||||
|
||||
With the default setting of `use_significance` set to `true`, the Graph API
|
||||
performs a background frequency check of the terms it discovers as part of
|
||||
|
|
|
|||
|
|
@ -32,8 +32,6 @@ include::{kib-repo-dir}/uptime/index.asciidoc[]
|
|||
|
||||
include::{kib-repo-dir}/siem/index.asciidoc[]
|
||||
|
||||
include::graph/index.asciidoc[]
|
||||
|
||||
include::dev-tools.asciidoc[]
|
||||
|
||||
include::monitoring/index.asciidoc[]
|
||||
|
|
|
|||
Loading…
Reference in a new issue