-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] not reporting when failed index #525
Comments
@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. As a note to us: telegraf uses v2 of opensearch-go |
As you can see in issue influxdata/telegraf#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 influxdata/telegraf#15119 (comment) |
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 influxdata/telegraf#15119 (comment). |
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 influxdata/telegraf#15119 influxdata/telegraf#14334
The text was updated successfully, but these errors were encountered: