.net client application log not creating index in elasticsearch

Hello Team,

we have .net application we used .net client elasticsearch to share the log to new index.

Recently we haven't received any new index created by .net application. there is no way to find the whether the index received or not.

The old index which was created before that is receiving logs continuously, but the new one not working.

Please help us to fix the issue.

Hi, @rajvel.

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?

Hello Steve,

The below is the format we have configured to send the application which was hosted on .Net to elasticsearch.
Most of the application uses serilog.

Is it possible to check whether the index creation is disabled or not via API.

"EINDEX": "test_log",
    "ETOKEN": "123455XXXXXXX==",
    "EURL": "http://test-dev.only.com:9200/",

                new ElasticsearchSinkOptions(new Uri(configuration["ApplicationSettings:EURL"].ToString()))
                    AutoRegisterTemplate = true,
                    IndexFormat = configuration["ApplicationSettings:EINDEX"].ToString(),
                    TypeName = null,
                    BatchAction = ElasticOpType.Create,
                    ModifyConnectionSettings = (c) =>
                        (o, certificate, arg3, arg4) => { return true; });
                        c.GlobalHeaders(new NameValueCollection { { "Authorization", "ApiKey " + configuration["ApplicationSettings:ETOKEN"].ToString() } });
                        return c;

@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.

Thanks for your time.

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.

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