-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Meta] Add more benchmark schema templates to integrations #8636
Comments
We have a low level issue: #8719 which will be closed (not immediately but after all the WIP PRs are done) and we can use this top level issue for tracking of all package level template additions. Right now adding Aliabbas as owner, please add anyone else as applicable. Also adding the issue into relevant project boards. |
Hi @ruflin, Since all the data streams benchmark schema templates are completed, can this issue be closed or any additional package(s) we should expand the scope it? |
This is great @lalit-satapathy Are the templates used to run benchmarks that we also look at from time to time? We can close this issue but lets make sure we follow up on actively using these templates for developing features and running benchmarks. |
In elastic/elastic-package#1476 the initial schema templates from the corpus generator repo were added to the integrations. Ideally all integrations would have templates but as this is not feasible, lets start small. This is a meta issue to track the top 5 integrations for which schemas should be added. The proposed list is:
Each of these integrations have quite a few datasets, for detailed tracking the datasets are listed below (this list might change over time). Adding these dataset will potentially also add new requirements to the corpus which is expected. These additions in combination with the stream command will allow anyone to test integrations against a running Elastic Stack instance. The expected outcome is that the integration dashboards show mostly "reasonable" data. It is not expected that necessarily cross linking is possible or the data shown makes a 100% sense. For example CPU usage might fluctuate faster then in reality.
Tracking: Dataset list
Below is the list of integrations and dataset for tracking. Lets add reference to PR or code if completed. For each integration, lets add the most important datasets.
The text was updated successfully, but these errors were encountered: