Entitas VS ecs

Github documentation for entitias looks like it is still good https://github.com/sschmid/Entitas-CSharp/wiki

For examples I usually turn to GitHub. It has numerous C# game engines. However, I find it easier to figure out implementations myself and use other engines only for API inspiration. There are also several C# ECS such as Entitas and DefaultECS that you can use if you do not want to create you own.

- Entitas

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,...