# Map custom date and time in Elasticsearch

Supported in:
After you and configure an integration, you must map its fields to
Google Security Operations fields to accurately display the information on the
platform. More specifically, this document explains how to map a custom date
and time for the Elasticsearch connector.


When you configure the **Elasticsearch** connector, you must *convert*
or map the custom date and time fields, such as *\\_source\\_@timestamps*, to
**startTime** and **endTime** of Google SecOps cases.

1. Go to **Settings \> Investigation \> Ontology Status**.
2. Click settings **Configure** in the same row as the Elasticsearch connector.
3. On the **Event Configuration** page, select **Mapping**.
4. Under **System Fields** , select the **StartTime** row and choose **Edit Field** from the menu.
5. In the **Map Target Field: StartTime** dialog, set the following fields:
   - **Extracted** : Select **\\_source\\_@timestamp**, which is from the ELK stack.
   - **Transformation Function** : Select **FROM_CUSTOM_DATETIME**.
   - **Enter Parameters** : Enter `YYYY-MM-DDTHH:MM:SS:zzzZ`.
6. In the **Map Target Field: EndTime** dialog, set the following fields:
   - **Extracted Field** : Select **\\_source\\_@timestamp**, which is from the ELK stack.
   - **Transformation Function** : Select **FROM_CUSTOM_DATETIME**.
   - **Enter Parameters** : Enter `YYYY-MM-DDTHH:MM:SS:zzzZ` to generalize the time format.
7. Click **Save**.


The Elasticsearch timestamp fields are now converted to the standardized time
and date fields.

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)