This repository was archived by the owner on Sep 17, 2024. It is now read-only.
Description After a demo of this framework, we'd like to create tests for Ingest Management, with the acknowledge of only supporting linux Docker containers.
We'll start with he current test script:
actual code / api / url / scripting
test case description / action
notes / pass fail
enable Fleet user and create initial Kibana setup
set (if needed) the kibana /es global settings
skip in prototype - we can use Default config + enrollment key to start if we want
add nginx package
skip in prototype
add new configuration
skip in prototype
add nginx data source to configuration, with some defaults
skip in prototype
get new enrollment key for that config
skip in prototype
get the whole enrollment string from Ingest
skip in prototype
transfer Agent binary, unzip it on host and enroll it with noted command, if easy que
In Kibana (or ES) query against Fleet API for the new Agent
then run the agent on host
do some minimal activity to trigger logs / metrics to be sent (open VIM save file, copy file, open bash, ping elastic.co, curl demo ES cluster
query ES to check the docs are there that relate to the dashboards for the given data stream
query in Kibana API in Fleet to see the agent shows up
from Kibana API, 'un-enroll Agent' . this will leave the agent running on the host, but connection will be refused and no new data will ship,
confirm no new data shows up in ES locations like what was used in prior steps
back on host - re-enroll the agent and re-run it.
skip in prototype
back in Kibana, confirm again that new data is showing up
skip in prototype
revoke the 'enrollment token'
skip in prototype
confirm again that no new data comes in that relates to the deployment done with the configuration that used that enrollment token
skip in prototype
stop agent on host, and ensure metricbeat & filebeat (and agent and endpoint) stop
cc/ @michalpristas @EricDavisX @ph
Reactions are currently unavailable
After a demo of this framework, we'd like to create tests for Ingest Management, with the acknowledge of only supporting linux Docker containers.
We'll start with he current test script:
enable Fleet user and create initial Kibana setup
set (if needed) the kibana /es global settings
add nginx package
add new configuration
add nginx data source to configuration, with some defaults
get new enrollment key for that config
get the whole enrollment string from Ingest
transfer Agent binary, unzip it on host and enroll it with noted command, if easy que
In Kibana (or ES) query against Fleet API for the new Agent
then run the agent on host
do some minimal activity to trigger logs / metrics to be sent (open VIM save file, copy file, open bash, ping elastic.co, curl demo ES cluster
query ES to check the docs are there that relate to the dashboards for the given data stream
query in Kibana API in Fleet to see the agent shows up
from Kibana API, 'un-enroll Agent' . this will leave the agent running on the host, but connection will be refused and no new data will ship,
confirm no new data shows up in ES locations like what was used in prior steps
back on host - re-enroll the agent and re-run it.
back in Kibana, confirm again that new data is showing up
revoke the 'enrollment token'
confirm again that no new data comes in that relates to the deployment done with the configuration that used that enrollment token
stop agent on host, and ensure metricbeat & filebeat (and agent and endpoint) stop
cc/ @michalpristas @EricDavisX @ph