SavedObjectsExportablePredicate<Attributes>
| Optional hook to specify whether an object should be exportable.If specified, isExportable
will be called during export for each of this type's objects in the export, and the ones not matching the predicate will be excluded from the export.When implementing both isExportable
and onExport
, it is mandatory that isExportable
returns the same value for an object before and after going though the export transform. E.g isExportable(objectBeforeTransform) === isExportable(objectAfterTransform)
|
| [onExport](./kibana-plugin-core-server.savedobjectstypemanagementdefinition.onexport.md) | SavedObjectsExportTransform<Attributes>
| An optional export transform function that can be used transform the objects of the registered type during the export process.It can be used to either mutate the exported objects, or add additional objects (of any type) to the export list.See [the transform type documentation](./kibana-plugin-core-server.savedobjectsexporttransform.md) for more info and examples.When implementing both isExportable
and onExport
, it is mandatory that isExportable
returns the same value for an object before and after going though the export transform. E.g isExportable(objectBeforeTransform) === isExportable(objectAfterTransform)
|
| [onImport](./kibana-plugin-core-server.savedobjectstypemanagementdefinition.onimport.md) | SavedObjectsImportHook<Attributes>
| An optional [import hook](./kibana-plugin-core-server.savedobjectsimporthook.md) to use when importing given type.Import hooks are executed during the savedObjects import process and allow to interact with the imported objects. See the [hook documentation](./kibana-plugin-core-server.savedobjectsimporthook.md) for more info. |
+| [visibleInManagement](./kibana-plugin-core-server.savedobjectstypemanagementdefinition.visibleinmanagement.md) | boolean
| When set to false, the type will not be listed or searchable in the SO management section. Main usage of setting this property to false for a type is when objects from the type should be included in the export via references or export hooks, but should not directly appear in the SOM. Defaults to true
. |
diff --git a/docs/development/core/server/kibana-plugin-core-server.savedobjectstypemanagementdefinition.visibleinmanagement.md b/docs/development/core/server/kibana-plugin-core-server.savedobjectstypemanagementdefinition.visibleinmanagement.md
new file mode 100644
index 0000000000000..33ddc8e8c8307
--- /dev/null
+++ b/docs/development/core/server/kibana-plugin-core-server.savedobjectstypemanagementdefinition.visibleinmanagement.md
@@ -0,0 +1,18 @@
+
+
+[Home](./index.md) > [kibana-plugin-core-server](./kibana-plugin-core-server.md) > [SavedObjectsTypeManagementDefinition](./kibana-plugin-core-server.savedobjectstypemanagementdefinition.md) > [visibleInManagement](./kibana-plugin-core-server.savedobjectstypemanagementdefinition.visibleinmanagement.md)
+
+## SavedObjectsTypeManagementDefinition.visibleInManagement property
+
+When set to false, the type will not be listed or searchable in the SO management section. Main usage of setting this property to false for a type is when objects from the type should be included in the export via references or export hooks, but should not directly appear in the SOM. Defaults to `true`.
+
+Signature:
+
+```typescript
+visibleInManagement?: boolean;
+```
+
+## Remarks
+
+`importableAndExportable` must be `true` to specify this property.
+
diff --git a/docs/osquery/images/enter-query.png b/docs/osquery/images/enter-query.png
new file mode 100644
index 0000000000000..154d2dcad4857
Binary files /dev/null and b/docs/osquery/images/enter-query.png differ
diff --git a/docs/osquery/images/live-queries-history.png b/docs/osquery/images/live-queries-history.png
new file mode 100644
index 0000000000000..6f49917a685d6
Binary files /dev/null and b/docs/osquery/images/live-queries-history.png differ
diff --git a/docs/osquery/images/live-query-check-results.png b/docs/osquery/images/live-query-check-results.png
new file mode 100644
index 0000000000000..df292309e0853
Binary files /dev/null and b/docs/osquery/images/live-query-check-results.png differ
diff --git a/docs/osquery/images/live-query-history.png b/docs/osquery/images/live-query-history.png
new file mode 100644
index 0000000000000..97d9ccb1bda88
Binary files /dev/null and b/docs/osquery/images/live-query-history.png differ
diff --git a/docs/osquery/images/play-icon.png b/docs/osquery/images/play-icon.png
new file mode 100644
index 0000000000000..724d17b5a381d
Binary files /dev/null and b/docs/osquery/images/play-icon.png differ
diff --git a/docs/osquery/images/schedule-query.png b/docs/osquery/images/schedule-query.png
new file mode 100644
index 0000000000000..51d83f2540aca
Binary files /dev/null and b/docs/osquery/images/schedule-query.png differ
diff --git a/docs/osquery/images/scheduled-query-groupds.png b/docs/osquery/images/scheduled-query-groupds.png
new file mode 100644
index 0000000000000..bb7fd8ae87563
Binary files /dev/null and b/docs/osquery/images/scheduled-query-groupds.png differ
diff --git a/docs/osquery/images/table-icon.png b/docs/osquery/images/table-icon.png
new file mode 100644
index 0000000000000..5c4e9e78d9f09
Binary files /dev/null and b/docs/osquery/images/table-icon.png differ
diff --git a/docs/osquery/osquery.asciidoc b/docs/osquery/osquery.asciidoc
new file mode 100644
index 0000000000000..1e4e6604a7c70
--- /dev/null
+++ b/docs/osquery/osquery.asciidoc
@@ -0,0 +1,419 @@
+[chapter]
+[role="xpack"]
+[[osquery]]
+= Osquery
+
+https://osquery.io[Osquery] is an open source tool that lets you query operating systems, like a database, providing you with visibility into your infrastructure and operating systems.
+Using basic SQL commands, you can ask questions about devices, such as servers,
+Docker containers, and computers running Linux, macOS, or Windows.
+The https://osquery.io/schema[extensive schema] helps with a variety of use cases,
+including vulnerability detection, compliance monitoring, incident investigations, and more.
+
+With Osquery, you can:
+
+ * Run live queries for one or more agents
+ * Schedule queries to capture changes to OS state over time
+ * View a history of past queries and their results
+ * Save queries and build a library of queries for specific use cases
+
+Osquery results are stored in {es}, so that you can
+search, analyze, and visualize Osquery data in {kib}.
+
+Osquery is powered by the *Osquery Manager* integration.
+For information on how to set up *Osquery Manager*, refer to <