[Feature Request] Include TSDB related tests as part of the test

[agithomas]

Adding two suggestions in the context of TSDB

• TSDB Test Toolkit is a very important toolset to validate the possibility of data drop when datasets are TSDB enabled. Can we perform TSDB test toolkit run as part of the system test for datasets with index_mode: "time_series" ?
• Include an additional check (elastic-package check)to validate If there exists type: metrics in manifest.yml, there is also index_mode: "time_series" . This can be overridden by a flag --no-tsdb. This ensures that all future contributions are having index_mode: time_series

[jsoriano]

• TSDB Test Toolkit is a very important toolset to validate the possibility of data drop when datasets are TSDB enabled. Can we perform TSDB test toolkit run as part of the system test for datasets with index_mode: "time_series" ?

It looks like this tool is implemented in Python. Is there a chance to migrate these checks to Go? This would help to include it as part of elastic-package test system.

If not possible, maybe another option is to run this as a separate process in CI.

• Include an additional check (elastic-package check)to validate If there exists type: metrics in manifest.yml, there is also index_mode: "time_series" . This can be overridden by a flag --no-tsdb. This ensures that all future contributions are having index_mode: time_series

I think we can add this restriction through the Package Spec, with the option to skip it through validation.yml config. We could also consider making Fleet to always set index_mode: "time_series" for data streams of type: metrics.

[agithomas]

It looks like this tool is implemented in Python. Is there a chance to migrate these checks to Go? This would help to include it as part of elastic-package test system.

@constanca-m , are there any reasons why you preferred Python over Go? Do you have plans for Go migration?

[constanca-m]

are there any reasons why you preferred Python over Go? Do you have plans for Go migration?

It was mainly because of elastic search client being more friendly for python, I believe. But if there is interest in a go version, I could build it as well