ecs VS go-elasticsearch

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

Deprecated: Use the official Elasticsearch client for Go at https://github.com/elastic/go-elasticsearch

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

Elasticsearch client for Go RabbitMQ Go RabbitMQ Client Library Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus Echo web framework Kibana is user interface that lets you visualize your Elasticsearch Docker and docker-compose Kubernetes K8s Helm The package manager for Kubernetes

PostgeSQL as event store database Kafka as messages broker gRPC Go implementation of gRPC Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus MongoDB MongoDB database Elasticsearch Elasticsearch client for Go. Echo web framework Kibana Kibana is data visualization dashboard software for Elasticsearch Migrate for migrations

did you use "github.com/elastic/go-elasticsearch/v8" package? for your project

elastic/go-elasticsearch 4.1k Starts, Used by 414

yeah it’s part of an ongoing slapfight between elastic co and amazon, see this PR https://github.com/elastic/go-elasticsearch/pull/324 and the many similar ones for all the other client libraries