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:
- system
- nginx
- k8s
- aws / aws_logs
- mysql
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.
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.