Add the local time zone
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
The add_locale processor enriches each event with either the machine’s time zone offset from UTC or the name of the time zone. The processor adds the a event.timezone value to each event.
The configuration adds the processor with the default settings:
- add_locale: ~
This configuration adds the processor and configures it to add the time zone abbreviation to events:
- add_locale:
format: abbreviation
The add_locale processor differentiates between daylight savings time (DST) and regular time. For example CEST indicates DST and and CET is regular time.
Elastic Agent processors execute before ingest pipelines, which means that they process the raw event data rather than the final event sent to Elasticsearch. For related limitations, refer to What are some limitations of using processors?
| Name | Required | Default | Description |
|---|---|---|---|
format |
No | offset |
Whether an offset or time zone abbreviation is added to the event. |