# Different time in copied index and pipeline **URL:** \ **Category:** Elastic Agent\ **Tags:** filebeat\ **Created:** [October 19, 2022, 10:02am UTC](https://discuss.elastic.co/t/different-time-in-copied-index-and-pipeline/316980 "2022-10-19T10:02:25Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![hermlam](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@hermlam](https://discuss.elastic.co/u/hermlam)\ **Post date:** [October 19, 2022, 10:02am UTC](https://discuss.elastic.co/t/different-time-in-copied-index-and-pipeline/316980/1 "2022-10-19T10:02:25Z")
I have something strange with timezones. From my raspberry Pi I am sending some specific information (temperature) to Sylog (separate Syslog Server). Same format as normal syslog: In my Syslog server I am splitting the logs sending two logs to Elastic: All logging from the Raspberry Pi; ' Oct 19 11:54:24 PiMirror piinfo: gpu\_temp=54.0;cpu\_temp=53.0;model=4 ' Oct 19 11:54:24 PiMirror sudo[4753]: pam\_unix(sudo:session): session closed for user root Specific logging. ' Oct 19 11:05:01 PiMirror piinfo: gpu\_temp=52.1;cpu\_temp=53.0;model=4 ' Oct 19 11:54:24 PiMirror piinfo: gpu\_temp=54.0;cpu\_temp=53.0;model=4 In Elastic I copied the Syslog ingest pipeline exactly to a specific pipeline and added a KV processor to this specific pipeline, to split the values; I made a copy of the syslog index and a 3 fields to it. All is working fine, a have a specific index for my Raspberry Pi info. But there is one problem, the specific index has a timestamp 2 hours ahead. That’s strange? Thanks, Herman ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 16, 2022, 10:02am UTC](https://discuss.elastic.co/t/different-time-in-copied-index-and-pipeline/316980/2 "2022-11-16T10:02:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.