Closed RodrigoDornelles closed 2 months ago
@RodrigoDornelles can you please give us more information and some clear instructions on how to reproduce this. Especially for ppl. who don't use telegraf. Moreover the http bulk response would be interesting.
As a note to us: telegraf uses v2 of opensearch-go
As you can see in issue https://github.com/influxdata/telegraf/issues/15119, using any configuration with valid syntax, but incorrect parameters such as password or host will reproduce the error.
who said there was a possibility that the problem could be in this plugin was @powersj with his comment https://github.com/influxdata/telegraf/issues/15119#issuecomment-2051713377
So this problem only happens with telegraf? If so sounds like an issue with that agent rather than a problem with the library itself. Any objections we close this here @RodrigoDornelles, or do you have reasons to believe the client is the issue?
I haven't tested it elsewhere, well if there is a feature that reports errors in the plugin, the error is certainly not here.
Looks like this was root caused in https://github.com/influxdata/telegraf/issues/15119#issuecomment-2057093872.
What is the bug?
How can one reproduce the bug?
There is no error log when there is a wrong configuration, such as failed SSL, wrong DNS, permission error...
What is the expected behavior?
correct config logs
wrong config logs
2024-04-08T14:00:03Z D! [outputs.opensearch] Indexed to OpenSearch with status- [201] Result- created DocumentID- c61b1e60c648cc1fc86222e059d36d89c3eee5db49d4d36b16a96d0fbbcc22b9
expected with wrong config logs
What is your host/environment?
Linux 5.15, Docker 26.0, Telegraf 1.30.1
Do you have any additional context?
issue related https://github.com/influxdata/telegraf/issues/15119 https://github.com/influxdata/telegraf/issues/14334