You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just wanna output log into my external ES with _type as doc not the default value _doc.
Refer to the es output plugin document , I create an Output.logging.kubesphere.io/v1alpha2 custom resource with spec.es.type value as "doc".
But, after the Output.logging.kubesphere.io/v1alpha2 custom resource apply, the flunent-bit pod print warn log [ warn] net_tcp_fd_connect: getaddrinfo(host='doc'): Name or service not known and output log not appear in my extrnal ES.
Versions Used
KubeSphere: v3.1.0
Kubernetes:
Environment
How many nodes and their hardware configuration:
For example: CentOS 7.5 / 3 masters: 8cpu/8g; 3 nodes: 8cpu/16g
(and other info are welcomed to help us debugging)
How To Reproduce
Steps to reproduce the behavior:
Install kubesphere
Install logging feature and config with extrnal ES
Create an Output.logging.kubesphere.io/v1alpha2 custom resource with blow yaml file:
Describe the Bug
I just wanna output log into my external ES with
_type
asdoc
not the default value_doc
.Refer to the es output plugin document , I create an
Output.logging.kubesphere.io/v1alpha2
custom resource withspec.es.type
value as "doc".But, after the
Output.logging.kubesphere.io/v1alpha2
custom resource apply, the flunent-bit pod print warn log[ warn] net_tcp_fd_connect: getaddrinfo(host='doc'): Name or service not known
and output log not appear in my extrnal ES.Versions Used
KubeSphere: v3.1.0
Kubernetes:
Environment
How many nodes and their hardware configuration:
For example: CentOS 7.5 / 3 masters: 8cpu/8g; 3 nodes: 8cpu/16g
(and other info are welcomed to help us debugging)
How To Reproduce
Steps to reproduce the behavior:
Output.logging.kubesphere.io/v1alpha2
custom resource with blow yaml file:Expected behavior
I just wanna output log into my external ES with
_type
asdoc
not the default value_doc
.The text was updated successfully, but these errors were encountered: