Daniel (dB.) Doubrovkine

@moharana-subhashree I could be wrong, but I don't think the plugin is actually capable of knowing that you want a data stream here, and it implies that you should create...

> but with this configuration it ideally shall create a index template and that index template could be used for data stream creation, is my understanding correct? will this be...

This is similar to https://github.com/opensearch-project/logstash-output-opensearch/issues/227, https://github.com/opensearch-project/logstash-output-opensearch/issues/179, https://github.com/opensearch-project/logstash-output-opensearch/issues/176, and possibly others. The generic 400 error is unfortunately not helpful. Is there more in the output? Enable `--debug`, can we get the...

@gaddehyd that would definitely be a bug! maybe some code that only gets executed on debug? what are the versions that you're using? post relevant logs with and without?

Thanks. This has to be a red herring and a timing problem where by enabling debug logs we end up doing something out of order. There's nothing I found in...

@gaddehyd the code should be modified to display the `@response_body`, this message is unfortunately not helpful

Here: https://github.com/opensearch-project/logstash-output-opensearch/blob/f45b8c753ac4366e91194c682c85ced3858c9792/lib/logstash/outputs/opensearch/http_client/pool.rb#L26C86-L27C10 It says ```ruby "Got response code '#{response_code}' contacting OpenSearch at URL '#{@url}'" ``` try changing it to ```ruby "Got response code '#{response_code}' contacting OpenSearch at URL '#{@url}, request:...

This is helpful! The error seems common, [SO says](https://stackoverflow.com/questions/47452770/no-handler-for-type-string-declared-on-field-name) that `string` was dropped in favor of `text` or `uuid` at some point a long time ago. So what's your initial...

I still would like a detailed repro so that we can actually improve the code to show the error here. Help us build one? Something super rudimentary with 5 steps...

Does the 2.4.1 come up? Is there another error in the logs?