# Utilize serilog sinks to elastic search

**URL:** <https://discuss.elastic.co/t/utilize-serilog-sinks-to-elastic-search/350969>\
**Category:** Elasticsearch\
**Created:** [January 12, 2024, 2:36pm UTC](https://discuss.elastic.co/t/utilize-serilog-sinks-to-elastic-search/350969 "2024-01-12T14:36:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![minh.tran](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@minh.tran](https://discuss.elastic.co/u/minh.tran)\
**Post date:** [January 12, 2024, 2:36pm UTC](https://discuss.elastic.co/t/utilize-serilog-sinks-to-elastic-search/350969/1 "2024-01-12T14:36:01Z")

</div>

Hi there, we are currently using seirlog elastic sink. Details can be found here [GitHub - serilog-contrib/serilog-sinks-elasticsearch: A Serilog sink that writes events to Elasticsearch](https://github.com/serilog-contrib/serilog-sinks-elasticsearch)

Is there a way we can make the sink respect the existing index templates? Any template defined gets overwritten on next submission. The main goal is so it can inherit exiting lifecycle policies and not overwrite.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 9, 2024, 2:36pm UTC](https://discuss.elastic.co/t/utilize-serilog-sinks-to-elastic-search/350969/2 "2024-02-09T14:36:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.