-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Elasticsearch sink not working #1211
Comments
I think what you should do is --sink=elasticsearch:?nodes=http://elasticsearch.es.svc.cluster.local:9200 |
i am having the same problem E0726 18:20:17.526386 1 factory.go:74] Failed to create sink: failed to create ElasticSearch client: no Elasticsearch node available --sink=elasticsearch:?nodes=http://foo.bar:9200&esUserName=foo&esUserSecret=bar |
I have same problem with or without specifying scheme. |
In my case it worked by specifying the nodes parameter, but also using the latest version. |
I did succeed to send metric to elasticsearch using 1.2.beta0. |
Still same issue with 1.2.beta1. |
Agreed with above comments, specifying index does not change it. Also metrics get pushed to index, but no events. Version 1.2.0, any progress on this issue. Also might be nice to be able to specify if you want metrics and events or only one of them. |
From v1.2.0-beta.0, the ES sink has been added to events. Any issues about this event ES sink? @douglasader |
Well I'm using 1.2.0, which is newer then 1.2.0-beta.0 AFAIK and events are not sent to ES, note however the index is setup on ES for events and metrics though, but only metrics gets populated with actual entries. |
cc @AlmogBaku |
|
I have setup an elk stack in its own namespace, aka
es
. And there is a service called:elasticsearch.es.svc.cluster.local
.For the sink option I simply use: `--sink=elasticsearch:http://elasticsearch.es.svc.cluster.local:9200". This does not work and i suppose it has to do with:
In case I and the
?nodes...
param, then I get:I have also tried to play with the sniff, timeouts etc options, so I'm stuck for the time being and the elasticsearch sink does not work
(Question: the nodes paramater seems to be mandatory? According to the
if len(opts["nodes"]) < 1
? Why is that?)The text was updated successfully, but these errors were encountered: