Closed marcio-pessoa closed 2 years ago
Just encountered this
Seems you need to provide FLUENT_OPENSEARCH_CA_PATH
and FLUENT_OPENSEARCH_CLIENT_*
values in your env
variables, or follow guidance in the readme ("Use your configuration) to remove those lines from /fluentd/etc/fluent.conf
, even though FLUENT_OPENSEARCH_SSL_VERIFY
is false
.
Your tip really help me @jm3dedalus Thank you very much!
After the change Fluentd connects to OpenSearch, but I got a lot of \\\\ on Fluentd logs. So, I added some parse configurations as environment variables:
- name: FLUENT_CONTAINER_TAIL_PARSER_TYPE
value: "cri"
- name: FLUENT_CONTAINER_TAIL_PARSER_TIME_FORMAT
value: "%Y-%m-%dT%H:%M:%S.%N%:z"
Now everything is working fine. Thanks again!
I just submitted a pull request with a working OpenSearch example, because the final definition file is really different of ElasticSearch example file.
Hi dears,
I'm trying to use Fluentd Daemonset for Kubernetes with OpenSearch 1.2.4.
Here are the DaemonSet definition:
After apply the yaml, I got some logs:
Could you help me to solve the warning
#0 [out_os] Could not communicate to OpenSearch, resetting connection and trying again. No such file or directory @ rb_sysopen - (Errno::ENOENT)
?The OpenSearch is working fine for other applications, I also tested the user and It's authenticating fine.
Thanks in advance.