ecs VS SqlQueryStress

Elastic Common Data Model (ECS) sample data: Although intended for the Elastic Stack, you can adapt these sample logs for use in Splunk. The repository contains logs from various sources, such as network traffic, security events, and web server logs: https://github.com/elastic/ecs/tree/master/generated/samples

// Base represents the base schema type defined by the Elastic Common Schema (ECS). // // See https://github.com/elastic/ecs/blob/main/schemas/base.yml type Base struct { Timestamp *time.Time json:"@timestamp" Tags string json:"tags,omitempty" Labels map[string]any json:"labels,omitempty" Message string json:"message,omitempty" }

To move ECS ahead, we're adding the latest data types from current Elasticsearch like wildcard (https://github.com/elastic/ecs/blob/master/experimental/generated/elasticsearch/7/template.json#L30) or histogram. It won't be successful if we are only tied to the common denominator of data types in terms of space efficiency, performance, features,...

Sample Log Generator: This tool generates synthetic logs that you can customize to fit your needs. While not real-world data, it can be useful for testing specific scenarios or queries: https://github.com/ErikEJ/SqlQueryStress

You could try SqlQueryStress to mock out your database interaction and then increase the threads to see how it handles and then use SP_WhoIsActive to see what you are waiting on while that test is running.

To simulate a simple workload, you can use powerful load testing tools like Locust, K6 or Apache JMeter where you can simulate even the most complex and realistic workload. To create a simple workload, a nice tool originally written by Adam Machanic is also available: SQL Query Stress.