SearchRequest
| |
+| dependencies | {
injectedMetadata: CoreStart['injectedMetadata'];
uiSettings: IUiSettingsClient;
}
| |
+
+Returns:
+
+`{
+ rest_total_hits_as_int: boolean;
+ ignore_unavailable: boolean;
+ ignore_throttled: boolean;
+ max_concurrent_shard_requests: any;
+ preference: any;
+ timeout: string | undefined;
+ index: any;
+ body: any;
+}`
+
diff --git a/docs/development/plugins/data/public/kibana-plugin-plugins-data-public.md b/docs/development/plugins/data/public/kibana-plugin-plugins-data-public.md
index e818fb009fb19..bc1eb9100e85c 100644
--- a/docs/development/plugins/data/public/kibana-plugin-plugins-data-public.md
+++ b/docs/development/plugins/data/public/kibana-plugin-plugins-data-public.md
@@ -40,6 +40,7 @@
| [getEsPreference(uiSettings, sessionId)](./kibana-plugin-plugins-data-public.getespreference.md) | |
| [getQueryLog(uiSettings, storage, appName, language)](./kibana-plugin-plugins-data-public.getquerylog.md) | |
| [getSearchErrorType({ message })](./kibana-plugin-plugins-data-public.getsearcherrortype.md) | |
+| [getSearchParamsFromRequest(searchRequest, dependencies)](./kibana-plugin-plugins-data-public.getsearchparamsfromrequest.md) | |
| [getTime(indexPattern, timeRange, options)](./kibana-plugin-plugins-data-public.gettime.md) | |
| [plugin(initializerContext)](./kibana-plugin-plugins-data-public.plugin.md) | |
diff --git a/docs/drilldowns/drilldowns.asciidoc b/docs/drilldowns/drilldowns.asciidoc
new file mode 100644
index 0000000000000..2687441c99340
--- /dev/null
+++ b/docs/drilldowns/drilldowns.asciidoc
@@ -0,0 +1,108 @@
+[[drilldowns]]
+== 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,
+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 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
+
+Drilldowns are {kib} actions that you configure and store
+in the dashboard saved object. Drilldowns are specific to the dashboard panel
+for which you create them—they are not shared across panels.
+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 <(
) =>
function ElementsLoadedTelemetry(props: ElementsLoadedTelemetryProps) {
const { telemetryElementCounts, workpad, telemetryResolvedArgs, ...other } = props;
+ const { error, pending } = telemetryElementCounts;
const [currentWorkpadId, setWorkpadId] = useState (
0
);
- if (
- workpadElementCount === 0 ||
- (resolvedArgsAreForWorkpad && telemetryElementCounts.pending === 0)
- ) {
+ if (workpadElementCount === 0 || (resolvedArgsAreForWorkpad && pending === 0)) {
setHasReported(true);
} else {
setHasReported(false);
}
- } else if (
- !hasReported &&
- telemetryElementCounts.pending === 0 &&
- resolvedArgsAreForWorkpad
- ) {
- if (telemetryElementCounts.error > 0) {
+ } else if (!hasReported && pending === 0 && resolvedArgsAreForWorkpad) {
+ if (error > 0) {
trackMetric(METRIC_TYPE.LOADED, [WorkpadLoadedMetric, WorkpadLoadedWithErrorsMetric]);
} else {
trackMetric(METRIC_TYPE.LOADED, WorkpadLoadedMetric);
}
setHasReported(true);
}
- });
+ }, [currentWorkpadId, hasReported, error, pending, telemetryResolvedArgs, workpad]);
return
+
+
+ {strings.getTitle()}
- {strings.getTitle()}
+
+ {componentTemplatesToDelete.map((name) => (
+
+ >
+
+
+
+ {dataStreamName}
+
+