Action
| The last action dispatched on the history stack. |
-| [block](./kibana-plugin-core-public.scopedhistory.block.md) | | (prompt?: string | boolean | History.TransitionPromptHook<HistoryLocationState> | undefined) => UnregisterCallback
| Not supported. Use [AppMountParameters.onAppLeave](./kibana-plugin-core-public.appmountparameters.onappleave.md). |
+| [block](./kibana-plugin-core-public.scopedhistory.block.md) | | (prompt?: string | boolean | History.TransitionPromptHook<HistoryLocationState> | undefined) => UnregisterCallback
| Add a block prompt requesting user confirmation when navigating away from the current page. |
| [createHref](./kibana-plugin-core-public.scopedhistory.createhref.md) | | (location: LocationDescriptorObject<HistoryLocationState>, { prependBasePath }?: {
prependBasePath?: boolean | undefined;
}) => Href
| Creates an href (string) to the location. If prependBasePath
is true (default), it will prepend the location's path with the scoped history basePath. |
| [createSubHistory](./kibana-plugin-core-public.scopedhistory.createsubhistory.md) | | <SubHistoryLocationState = unknown>(basePath: string) => ScopedHistory<SubHistoryLocationState>
| Creates a ScopedHistory
for a subpath of this ScopedHistory
. Useful for applications that may have sub-apps that do not need access to the containing application's history. |
| [go](./kibana-plugin-core-public.scopedhistory.go.md) | | (n: number) => void
| Send the user forward or backwards in the history stack. |
diff --git a/docs/user/alerting/defining-alerts.asciidoc b/docs/user/alerting/defining-alerts.asciidoc
index ed0e2966b22882..acfb26d2e11b39 100644
--- a/docs/user/alerting/defining-alerts.asciidoc
+++ b/docs/user/alerting/defining-alerts.asciidoc
@@ -22,12 +22,16 @@ image::images/alert-flyout-sections.png[The three sections of an alert definitio
All alert share the following four properties in common:
[role="screenshot"]
-image::images/alert-flyout-general-details.png[alt='All alerts have name, tags, check every, and notify every properties in common']
+image::images/alert-flyout-general-details.png[alt='All alerts have name, tags, check every, and notify properties in common']
Name:: The name of the alert. While this name does not have to be unique, the name can be referenced in actions and also appears in the searchable alert listing in the management UI. A distinctive name can help identify and find an alert.
Tags:: A list of tag names that can be applied to an alert. Tags can help you organize and find alerts, because tags appear in the alert listing in the management UI which is searchable by tag.
Check every:: This value determines how frequently the alert conditions below are checked. Note that the timing of background alert checks are not guaranteed, particularly for intervals of less than 10 seconds. See <
+ This example shows how you can use
+ Start a long-running search, save the session and then restore it. See how fast search
+ is completed when restoring the session comparing to when doing initial search.
+
+ Follow this demo step-by-step:{' '}
+ configure the query, start the search and then save your session. You can save
+ your session both when search is still in progress or when it is completed. After you
+ save the session and when initial search is completed you can{' '}
+ restore the session: the search will re-run reusing previous results. It will
+ finish a lot faster then the initial search. You can also{' '}
+ go to search sessions management and get back to the stored results from
+ there.
+
+ This demo works best with
+ We recommend to enable it in your