LogsDB functional tests #203716
Assignees
Labels
Team:Kibana Management
Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Comments
mattkime
added
the
Team:Kibana Management
|
Pinging @elastic/kibana-management (Team:Kibana Management) |
5 tasks
|
I read in different test cases that Note that this is not expected to happen automatically. ROllover will either happen according to the rollover policy of the data stream or it will need to be triggered explicitly. |
|
Would it make sense to have a test that explicitly triggers the rollover operation? |
SoniaSanzV
added a commit
that referenced
this issue
Dec 30, 2024
Part of #203716 ## Summary * Functional test for verifying that users can create indices using the “logsdb” index mode via the Kibana interface (Stateful and serverless). * Functional test for verifying that users can upgrade a logs data stream that is using a “standard” index mode to a data stream using “logsdb” index mode. (Stateful and serverless). * Functional test for verifying that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “standard” index mode. (Stateful and serverless). * Functional test for verifying that users can upgrade a data stream that is using a “time series” index mode to a data stream using “logsdb” index mode. (Stateful and serverless). * Functional test for verifying that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “time series” index mode. (Stateful and serverless). The rollover operation has not been tested since is not expected to happen automatically. See [this comment](#203716 (comment)).
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Dec 30, 2024
Part of elastic#203716 ## Summary * Functional test for verifying that users can create indices using the “logsdb” index mode via the Kibana interface (Stateful and serverless). * Functional test for verifying that users can upgrade a logs data stream that is using a “standard” index mode to a data stream using “logsdb” index mode. (Stateful and serverless). * Functional test for verifying that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “standard” index mode. (Stateful and serverless). * Functional test for verifying that users can upgrade a data stream that is using a “time series” index mode to a data stream using “logsdb” index mode. (Stateful and serverless). * Functional test for verifying that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “time series” index mode. (Stateful and serverless). The rollover operation has not been tested since is not expected to happen automatically. See [this comment](elastic#203716 (comment)). (cherry picked from commit 34341e5)
stratoula
pushed a commit
to stratoula/kibana
that referenced
this issue
Jan 2, 2025
Part of elastic#203716 ## Summary * Functional test for verifying that users can create indices using the “logsdb” index mode via the Kibana interface (Stateful and serverless). * Functional test for verifying that users can upgrade a logs data stream that is using a “standard” index mode to a data stream using “logsdb” index mode. (Stateful and serverless). * Functional test for verifying that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “standard” index mode. (Stateful and serverless). * Functional test for verifying that users can upgrade a data stream that is using a “time series” index mode to a data stream using “logsdb” index mode. (Stateful and serverless). * Functional test for verifying that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “time series” index mode. (Stateful and serverless). The rollover operation has not been tested since is not expected to happen automatically. See [this comment](elastic#203716 (comment)).
benakansara
pushed a commit
to benakansara/kibana
that referenced
this issue
Jan 2, 2025
Part of elastic#203716 ## Summary * Functional test for verifying that users can create indices using the “logsdb” index mode via the Kibana interface (Stateful and serverless). * Functional test for verifying that users can upgrade a logs data stream that is using a “standard” index mode to a data stream using “logsdb” index mode. (Stateful and serverless). * Functional test for verifying that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “standard” index mode. (Stateful and serverless). * Functional test for verifying that users can upgrade a data stream that is using a “time series” index mode to a data stream using “logsdb” index mode. (Stateful and serverless). * Functional test for verifying that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “time series” index mode. (Stateful and serverless). The rollover operation has not been tested since is not expected to happen automatically. See [this comment](elastic#203716 (comment)).
cqliu1
pushed a commit
to cqliu1/kibana
that referenced
this issue
Jan 2, 2025
Part of elastic#203716 ## Summary * Functional test for verifying that users can create indices using the “logsdb” index mode via the Kibana interface (Stateful and serverless). * Functional test for verifying that users can upgrade a logs data stream that is using a “standard” index mode to a data stream using “logsdb” index mode. (Stateful and serverless). * Functional test for verifying that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “standard” index mode. (Stateful and serverless). * Functional test for verifying that users can upgrade a data stream that is using a “time series” index mode to a data stream using “logsdb” index mode. (Stateful and serverless). * Functional test for verifying that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “time series” index mode. (Stateful and serverless). The rollover operation has not been tested since is not expected to happen automatically. See [this comment](elastic#203716 (comment)).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need functional tests that cover the following cases, on both stateful and serverless.
Verify that users can create indices using the “logsdb” index mode via the Kibana interface. Functional test for create a logdb index #204788
Verify that users can upgrade a logs data stream that is using a “standard” index mode to a data stream using “logsdb” index mode. The data stream is expected to go through a rollover operation. Functional test for create a logdb index #204788
Verify that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “standard” index mode. The data stream is expected to go through a rollover operation. Functional test for create a logdb index #204788
Verify that users can upgrade a data stream that is using a “time series” index mode to a data stream using “logsdb” index mode. The data stream is expected to go through a rollover operation and new data to be indexed in the logs index only after the last time series index “end time” has lapsed. Functional test for create a logdb index #204788
Verify that users can downgrade a data stream that is using a “logsdb” index mode to a data stream using “time series” index mode. The data stream is expected to go through a rollover operation. Functional test for create a logdb index #204788
Verify that users can create snapshots from an LogsDB index.
Verify that users can restore a LogsDB snapshot.
Verify that users can create a source-only snapshot from a LogsDB index.
Verify that users can restore a source-only snapshot from a LogsDB index.
Verify that users can override index sorting using logs@custom.
Verify that users cannot disable synthetic source for a LogsDB index.
Verify that users can override LogsDB index settings including: ignore_above, ignore_malformed, ignore_dynamic_beyond_limit, subobjects and timestamp format.
The text was updated successfully, but these errors were encountered: