[Docs] URL Drilldown

docs/user/dashboard/dashboard-drilldown.asciidoc

@@ -0,0 +1,78 @@
+[[dashboard-drilldown]]
+=== Dashboard Drilldown
+
+The dashboard drilldown allows you to navigate from one dashboard to another dashboard.
+
+For example, you might have a dashboard that shows the overall status of multiple data centers.
+You can create a drilldown that navigates from this dashboard to a dashboard
+that shows a single data center or server.
+
+This example shows a dashboard panel that contains a pie chart with a configured dashboard drilldown:
+
+[role="screenshot"]
+image::images/drilldown_on_piechart.gif[Drilldown on pie chart that navigates to another dashboard]
+
+[float]
+[[drilldowns-example]]
+==== Try it: Create a dashboard drilldown
+
+This example shows how to create the *Host Overview* drilldown shown earlier.
+
+
+*Set up the dashboards*
+
+. Add the <<gs-get-data-into-kibana, sample web logs>> data set.
+
+. Create a new dashboard, called `Host Overview`, and include these visualizations
+from the sample data set:
++
+[%hardbreaks]
+*[Logs] Heatmap*
+*[Logs] Visitors by OS*
+*[Logs] Host, Visits, and Bytes Table*
+*[Logs] Total Requests and Bytes*
++
+TIP: If you don’t see data for a panel, try changing the time range.
+
+. Open the *[Logs] Web traffic* dashboard.
+
+. Set a search and filter.
++
+[%hardbreaks]
+Search: `extension.keyword:( “gz” or “css” or “deb”)`
+Filter: `geo.src : CN`
+
+
+*Create the drilldown*
+
+
+. In the dashboard menu bar, click *Edit*.
+
+. In *[Logs] Visitors by OS*, open the panel menu, and then select *Create drilldown*.
+
+. Pick *Go to dashboard* action.
+
+. Give the drilldown a name.
+
+. Select *Host Overview* as the destination dashboard.
+
+. Keep both filters enabled so that the drilldown carries over the global filters and date range.
++
+Your input should look similar to this:
++
+[role="screenshot"]
+image::images/drilldown_create.png[Create drilldown with entries for drilldown name and destination]
+
+. Click *Create drilldown.*
+
+. Save the dashboard.
++
+If you don’t save the drilldown, and then navigate away, the drilldown is lost.
+
+. In *[Logs] Visitors by OS*, click the `win 8` slice of the pie, and then select the name of your drilldown.
++
+[role="screenshot"]
+image::images/drilldown_on_panel.png[Drilldown on pie chart that navigates to another dashboard]
++
+You are navigated to your destination dashboard. Verify that the search query, filters,
+and time range are carried over.

docs/user/dashboard/dashboard.asciidoc

@@ -463,6 +463,8 @@ include::edit-dashboards.asciidoc[]
 
 include::explore-dashboard-data.asciidoc[]
 
+include::drilldowns.asciidoc[]
+
 include::share-dashboards.asciidoc[]
 
 include::tutorials.asciidoc[]

docs/user/dashboard/drilldowns.asciidoc

@@ -1,20 +1,19 @@
-[float]
 [[drilldowns]]
-=== Use drilldowns for dashboard actions
+== Use drilldowns for dashboard actions
 
 Drilldowns, also known as custom actions, allow you to configure a
 workflow for analyzing and troubleshooting your data.
-Using a drilldown, you can navigate from one dashboard to another,
+For example, using a drilldown, you can navigate from one dashboard to another,
 taking the current time range, filters, and other parameters with you,
 so the context remains the same. You can continue your analysis from a new perspective.
 
-For example, you might have a dashboard that shows the overall status of multiple data centers.
+You might have a dashboard that shows the overall status of multiple data centers.
 You can create a drilldown that navigates from this dashboard to a dashboard
 that shows a single data center or server.
 
 [float]
 [[how-drilldowns-work]]
-==== How drilldowns work
+=== How drilldowns work
 
 Drilldowns are user-configurable {kib} actions that are stored with the
 dashboard metadata. Drilldowns are specific to the dashboard panel
@@ -24,8 +23,7 @@ A panel can have multiple drilldowns.
 This example shows a dashboard panel that contains a pie chart.
 Typically, clicking a pie slice applies the current filter.
 When a panel has a drilldown, clicking a pie slice opens a menu with
-the default action and your drilldowns. Refer to the <<drilldowns-example, Try it section>>
-for instructions on how to create this drilldown.
+the default action and your drilldowns.
 
 [role="screenshot"]
 image::images/drilldown_on_piechart.gif[Drilldown on pie chart that navigates to another dashboard]
@@ -36,7 +34,7 @@ to learn how to code drilldowns.
 
 [float]
 [[create-manage-drilldowns]]
-==== Create and manage drilldowns
+=== Create and manage drilldowns
 
 Your dashboard must be in *Edit* mode to create a drilldown.
 Once a panel has at least one drilldown, the menu also includes a *Manage drilldowns* action
@@ -46,61 +44,35 @@ for editing and deleting drilldowns.
 image::images/drilldown_menu.png[Panel menu with Create drilldown and Manage drilldown actions]
 
 [float]
-[[drilldowns-example]]
-==== Try it: Create a drilldown
-
-This example shows how to create the *Host Overview* drilldown shown earlier in this doc.
-
-*Set up the dashboards*
-
-. Add the <<gs-get-data-into-kibana, sample web logs>> data set.
+[[actions]]
+=== Drilldown actions
 
-. Create a new dashboard, called `Host Overview`, and include these visualizations
-from the sample data set:
-+
-[%hardbreaks]
-*[Logs] Heatmap*
-*[Logs] Visitors by OS*
-*[Logs] Host, Visits, and Bytes Table*
-*[Logs] Total Requests and Bytes*
-+
-TIP: If you don’t see data for a panel, try changing the time range.
+You can pick a drilldown action:
 
-. Open the *[Logs] Web traffic* dashboard.
-
-. Set a search and filter.
-+
-[%hardbreaks]
-Search: `extension.keyword:( “gz” or “css” or “deb”)`
-Filter: `geo.src : CN`
+[role="screenshot"]
+image::images/drilldown_pick_an_action.png[Pick a drilldown action]
 
-*Create the drilldown*
+Drilldown action defines behavior of your drilldown. {kib} provides the following types of actions:
 
-. In the dashboard menu bar, click *Edit*.
+[cols="2"]
+|===
 
-. In *[Logs] Visitors by OS*, open the panel menu, and then select *Create drilldown*.
+a| <<dashboard-drilldown, Dashboard drilldown>>
 
-. Give the drilldown a name.
+| Navigate to a dashboard. 
 
-. Select *Host Overview* as the destination dashboard.
+a| <<url-drilldown, URL drilldown>>
 
-. Keep both filters enabled so that the drilldown carries over the global filters and date range.
-+
-Your input should look similar to this:
-+
-[role="screenshot"]
-image::images/drilldown_create.png[Create drilldown with entries for drilldown name and destination]
+| Navigate to external or internal URL.
 
-. Click *Create drilldown.*
+|===
 
-. Save the dashboard.
-+
-If you don’t save the drilldown, and then navigate away, the drilldown is lost.
+[NOTE]
+==============================================
+Some action types are paid commercial features, while others are free.
+For a comparison of the Elastic subscription levels,
+see https://www.elastic.co/subscriptions[the subscription page].
+==============================================
 
-. In *[Logs] Visitors by OS*, click the `win 8` slice of the pie, and then select the name of your drilldown.
-+
-[role="screenshot"]
-image::images/drilldown_on_panel.png[Drilldown on pie chart that navigates to another dashboard]
-+
-You are navigated to your destination dashboard. Verify that the search query, filters,
-and time range are carried over.
+include::dashboard-drilldown.asciidoc[]
+include::url-drilldown.asciidoc[]

docs/user/dashboard/explore-dashboard-data.asciidoc

@@ -16,5 +16,3 @@ The data that displays depends on the element that you inspect.
 image:images/Dashboard_inspect.png[Inspect in dashboard]
 
 include::explore-underlying-data.asciidoc[]
-
-include::drilldowns.asciidoc[]