This version of the OpenSearch documentation is no longer maintained. For the latest version, see the current documentation. For information about OpenSearch version maintenance, see Release Schedule and Maintenance Policy.
date processor adds a default timestamp to an event, parses timestamp fields, and converts timestamp information to the International Organization for Standardization (ISO) 8601 format. This timestamp information can be used as an event timestamp. The following table describes the options you can use to configure the
|match||Conditionally||List||List of |
|from_time_received||Conditionally||Boolean||A boolean that is used for adding default timestamp to event data from event metadata which is the time when source receives the event. Default value is |
|destination||No||String||Field to store the timestamp parsed by date processor. It can be used with both |
|source_timezone||No||String||Time zone used to parse dates. It is used in case the zone or offset cannot be extracted from the value. If the zone or offset are part of the value, then timezone is ignored. Find all the available timezones the list of database time zones in the TZ database name column.|
|destination_timezone||No||String||Timezone used for storing timestamp in |
|locale||No||String||Locale is used for parsing dates. It’s commonly used for parsing month names( |
The following table describes common Abstract processor metrics.
| ||Counter||Metric representing the ingress of records to a pipeline component.|
| ||Counter||Metric representing the egress of records from a pipeline component.|
| ||Timer||Metric representing the time elapsed during execution of a pipeline component.|
date processor includes the following custom metrics.
dateProcessingMatchSuccessCounter: Returns the number of records that match with at least one pattern specified by the
dateProcessingMatchFailureCounter: Returns the number of records that did not match any of the patterns specified by the
patterns matchconfiguration option.