search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.65k stars 8.23k forks source link

[Lens][LogsDB] Provide testing coverage #193986

Closed dej611 closed 1 month ago

dej611 commented 1 month ago

Describe the feature:

Provide a similar FTR testing coverage as for TSDB also for the LogsDB feature. A summary list of tests of interest:

LOGSDB_KIB_01: verify that users can create indices using the “logs” index mode via the Kibana interface.

LOGSDB_KIB_02: verify that users can upgrade a logs data stream that is using a “standard” index mode to a data stream using “logs” index mode. The data stream is expected to go through a rollover operation.

LOGSDB_KIB_03: verify that users can downgrade a data stream that is using a “logs” index mode to a data stream using “standard” index mode. The data stream is expected to go through a rollover operation.

LOGSDB_KIB_04: verify that users can upgrade a data stream that is using a “time series” index mode to a data stream using “logs” 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.

LOGSDB_KIB_05: verify that users can downgrade a data stream that is using a “logs” index mode to a data stream using “time series” index mode. The data stream is expected to go through a rollover operation.

LOGSDB_KIB_06: verify that users can install a new integration using LogsDB and that all templates are properly installed.

LOGSDB_KIB_07: verify that users can remove an integration using LogsDB and that all templates are properly removed and that there is no template using LogsDB.

LOGSDB_KIB_20: verify that dashboards are loaded with expected latency performance when fetching data from LogsDB indices.

LOGSDB_KIB_21: verify that dashboards are loaded with expected latency performance when fetching data from a data stream with mixed type indices (standard and LogsDB).

LOGSDB_KIB_22: verify that dashboards are loaded with expected latency performance when fetching data from a data stream with mixed type indices (time series and LogsDB).

LOGSDB_KIB_23: verify that users can execute different queries on a LogsDB index (as if they are using a standard index).

LOGSDB_KIB_24: verify that users can execute any query on a LogsDB index applying filters on different fields, including host.name and @timestamp.

LOGSDB_KIB_25: verify that users can use a LogsDB index for an annotation layer using host.name and @timestamp.

LOGSDB_KIB_26: verify that users can create a ES|QL panel on dashboard using any combination of STATS operations w/o host.name and @timestamp fields.

LOGSDB_KIB_27: verify that users can execute any query on a LogsDB index applying filters on different fields, including host.name and @timestamp.

LOGSDB_KIB_28: verify that creating a mapping for LogsDB without host.name and @timestamp fields, these will appear nonetheless in the fields list within the “empty” category.

Things like latency expectations can be likely be ignored for a first iteration.

Describe a specific use case for the feature:

elasticmachine commented 1 month ago

Pinging @elastic/kibana-visualizations (Team:Visualizations)