Therefore, I could not find anything in the Elasticsearch documentation regarding the value of using a prefix @for field names (if there is a document about this, my question may have a simple answer).
I saw that it was used in the cases when the field is something about a log line - a simple example @timestamp, in the case of magazines AWS Cloudwatchon AWS Elasticsearch Serviceit sends things like @log_group, @idetc.
It would be interesting to know if using a character is @just a naming convention (someone decided to distinguish the meta-information of the log line from the corresponding fields) or if there is any functional difference in prefixing the field name with @.
Any insights (or answers)?
source
share