# Log mapping Centralizing logs from different technologies and applications can create dozens or hundreds of different attributes in a log management environment, especially when multiple teams are working in the same environment. For example, Host server name information can have many other names such as beat.hostname, hostname, host, syslog.hostname,... To unify the names for these properties, use Log mapping. Log mapping is pre-defined by us through common properties including: | **Portal reserved attributes** | **System fields** | | ------------------------------ | ------------------------------------------------------------------------------------------------- | | Nội dung | message, request.body | | Date | date, Timestamp, @timestamp, syslog.timestamp, eventTime, published\_date, \_timestamp, timestamp | | Host | beat.hostname, hostname, host, syslog.hostname | | Service | fields.service, service, syslog.appname | If you would like to add mapping for a certain property, please contact us. Adding this Log mapping attribute can be accommodated by us if your mapping attribute is reasonable through our review. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.vngcloud.vn/vng-cloud-document/vmonitor/dashboards/logs/lam-viec-voi-log-project/log-mapping.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.