1bf39845da
## Summary This PR introduces the first building blocks for the [Entity Analytics Privileged Monitoring](https://github.com/elastic/security-team/issues/9971). We follow the approach used in the Entity Store and add a new "Engine", which consists of the following components: * Public API * INIT and HEALTH routes * Kibana task * Privilege Monitoring Data Client * Engine Saved Object * API key manager * Related storage indices * Feature Flag: `privilegeMonitoringEnabled` set to `false` by default. * API integration test configuration * only tests that the health endpoint is available * Auditing and Telemetry ## Testing steps 1. Make sure to add `privilegeMonitoringEnabled` to your `kibana.dev.yaml` 2. In devtools, ensure the API is working with `GET kbn:/api/entity_analytics/monitoring/privileges/health` 3. Start the engine with: `POST kbn:/api/entity_analytics/monitoring/engine/init` 4. Look for `DEBUG` logs mentioning the `entity_analytics:monitoring:privileges:engine` task --------- Co-authored-by: CAWilson94 <charlotte.wilson@elastic.co> Co-authored-by: Charlotte Alexandra Wilson <CAWilson94@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| examples | ||
| linters | ||
| output | ||
| overlays | ||
| scripts | ||
| bundle.json | ||
| bundle.serverless.json | ||
| kibana.info.serverless.yaml | ||
| kibana.info.yaml | ||
| makefile | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
Kibana API reference documentation
Documentation about our OpenAPI bundling workflow and configuration. See Kibana's hosted stateful and serverless docs.
Workflow
The final goal of this workflow is to produce an OpenAPI bundle containing all Kibana's public APIs.
Step 0
OAS from Kibana's APIs are continuously extracted and captured in bundle.json and bundle.serverless.json as fully formed OAS documentation. See node scripts/capture_oas_snapshot --help for more info.
These bundles form the basis of our OpenAPI bundles to which we append and layer extra information before publishing.
Step 1
Append pre-existing bundles not extracted from code using kbn-openapi-bundler to produce the final resulting bundles.
To add more files into the final bundle, edit the appropriate oas_docs/scripts/merge*.js files.
Step 2
Apply any final overalys to the document that might include examples or final tweaks (see the "Scripts" section for more details).
Scripts
The oas_docs/scripts folder contains scripts that point to the source domain-specific OpenAPI bundles and specify additional parameters for producing the final output bundle. Currently, there are the following scripts:
-
merge_ess_oas.jsscript produces production an output bundle for ESS -
merge_serverless_oas.jsscript produces production an output bundle for Serverless
Output Kibana OpenAPI bundles
The oas_docs/output folder contains the final resulting Kibana OpenAPI bundles
kibana.yamlproduction ready ESS OpenAPI bundlekibana.serverless.yamlproduction ready Serverless OpenAPI bundle
Bundling commands
Besides the scripts in the oas_docs/scripts folder, there is an oas_docs/makefile to simplify the workflow. Use make help to see available commands.