Security Analytics

https://github.com/opensearch-project/security-analytics (this is where the project is. open source)
Task:
Field Aliases Creation
Sub-Items:
Create Index Level Mapping
Description
Use Field Aliases to rename the fields at run time without having to perform ingest time transformation

Security Analytics, a new open source intelligent threat detection service that helps customers protect their on-premise and cloud native application workloads by continuously monitoring application, network, system and other logs for malicious and unauthorized behavior. Security Analytics comes with a rich collection of detectors to identify a wide variety of tactics and techniques (MITRE ATT&CK) which are customizable and extensible by security practitioners. Security Analytics provides a simple interface to integrate with the existing event management and workflow systems. Security Analytics extensibility and feature velocity is further exacerbated by community support, community contributions, and knowledge sharing. OpenSearch, a free open-source database search analytics engine allows users the flexibility to run in both on-premise and cloud infrastructures and reduces a chance of vendor lock-in.

Field Aliases Reference and Usage of Field Aliases during Search Reference:
https://www.elastic.co/blog/introducing-field-aliases-in-elasticsearch
https://www.elastic.co/guide/en/elasticsearch/reference/7.0/alias.html
Changing the name of a field typically requires all documents containing the field to be reindexed, a potentially expensive undertaking. If it happens to be using time-based indexing, we can use field aliases to rename the field without having to reindex old data. The process works as in the attached screenshot

Alias Datatype:
https://www.elastic.co/guide/en/elasticsearch/reference/7.0/alias.html

Elastic Search Format：
https://www.elastic.co/blog/introducing-the-elastic-common-schema

Index Mapping API：
https://opensearch.org/docs/latest/opensearch/rest-api/index-apis/put-mapping/