You haven't provided enough context to provide any advice here. Are you creating the new index using the client and indexing documents? Can you share some code? Documents will be indexed to the index name you provide for the index/bulk/etc. methods you call. If the old index is continuing to receive new documents, have you ensured that you have specified the new index name when ingesting the data?
@rajvel You're using the Serilog.Sinks.Elasticsearch library, a third-party logging library not owned or supported by Elastic. Therefore, you'd be best placed to raise questions within the repo or potentially somewhere more general, such as StackOverflow.
Based on a cursory look, I'd expect your logs to be indexed into an index named "test_log" per your configuration. It doesn't include a placeholder for any other dynamic information for the index name.
The specified index need to be created but in my case its not happening.
For the same application if the application team forwarded the log its visible.
I am suspecting there is some cluster setting blocked to create a new indices.
COuld you please share is there any command to check on the cluster status.
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.