Graylog2 / Graylog2/graylog2-server

Flexible Date Converter cuts off milliseconds

Open
#2,323 2 comments 0 reactions 0 assignees View on GitHub
bug known issue P3 processing S3 triaged
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

### Problem description

if _flexibly parse date_ is used in extractor it cut offs the last digits of time.

2016-06-01T14:10:37.**579Z** will be 2016-06-01T14:10:37.**000Z**

![message_time_extract](https://cloud.githubusercontent.com/assets/404238/15715253/1507e070-281e-11e6-81d1-88644bfd9419.png)
### Steps to reproduce the problem
1. create _copy input_ extractor on a time field
2. extraction strategy _copy_
3. add converter _flexibly parse date_, timezone _UTC_
### Environment
- Graylog Version: 2.0.2
- Operating System: OVA

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.