I´m not sure I understand what you need to do. You need to overwrite a field you extract from your message with logstash's @timestamp? Why not use the @timestamp field itself where needed, instead? I´m afraid I must have misunderstood you.
Now, could you please post
your pipeline code,
and a sample of your expected output
so we can better help you?
Please, use the "</>" tool to format your code, samples, etc.
The next question is why you want to replace logstash's @timestamp. It is not recommended (don't know exactly why, I think it has to do with the relationship with the other elements of the ELK stack) and instead you should have a new field with your time. You'll get this field directly out of the grok{} filter I suggested above.
Sure , i will do and can you say how to create new field(Time) and assign to extracted timestamp from message body context . if you write sample lines it really helps me
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.