How to connect Jaeger to secured Elasticsearch - elasticsearch

My Elasticsearch cluster is secured with HTTPS and Basic Auth. I'd like to connect jaeger-ingester and jaeger-query on it.
I tried setting:
es.server-urls=https://elasticsearch:9200
es.tls.enabled=true
es.username=jaeger
es.password=XXXX
But I get:
{"level":"fatal","ts":1626344336.0828998,"caller":"command-line-arguments/main.go:65","msg":"Failed to init storage factory","error":"failed to create primary Elasticsearch client: health check timeout: no Elasticsearch node available","stacktrace":"main.main.func1\n\tcommand-line-arguments/main.go:65\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/cobra#v0.0.7/command.go:838\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/cobra#v0.0.7/command.go:943\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/cobra#v0.0.7/command.go:883\nmain.main\n\tcommand-line-arguments/main.go:114\nruntime.main\n\truntime/proc.go:225"}
This error message is not helpful.
How can I debug storage connection initialisation?

Related

Is there a way to connect to elastic search via jaeger collector using kerbros based auth mechanism?

Say, the elastic search cluster is secured via kerbros based authentication. So, how do I configure the jaeger collector and jaeger query to connect to the elastic search index?

i can't connect redis with phpfpm in kubernetes

I am trying to connect redis with phpfpm in kubernetes but I can`t, it shows the connection timeout as you shown in the picture

Error during WebSocket handshake,Unexpected response code: 502 using elasticache redis and elastic beanstalk

I am using django channels 2 and it is currenly working on localhost when I am using a redis server in Ubuntu in localhost. I had deployed my django project on elastic beanstalk and I am using elasticache redis 5. I have followed these tutorials https://hackernoon.com/setting-up-django-channels-on-aws-elastic-beanstalk-716fd5a49c4a and https://medium.com/#anish.shrestha/django-channels-2-0-and-aws-elastic-beanstalk-ab814bb15c4b. My .ebextesions has configurations env.config file and setup.config and daemon.config as shown in the tutorials. I have set the elastic beanstalk instance and elasticache redis on the same vpc and availability zone. I have set the inbound rule of the security groups to receive tcp on port 6379. Still I get the error of websocket unable to connect. This is the snapshot of how I am sending request to channels websocket connection. It works on localhost I am having trouble getting it to work on aws elasticache and elastic beanstalk. If anyone can provide some guidance that would be really helpful I am stuck on this for quite a long time now.

Kibana unable to connect to Elasticsearch

I am having trouble getting Kibana to connect to elasticsearch. The error I get is below;
plugin:elasticsearch#5.6.1 Request Timeout after 3000ms
Elasticsearch has been deployed via kubernetes and runs as a service called monitoring-es with a cluster IP of 100.63.124.194.
In my Kibana.yml file I have set the elasticsearch url as;
elasticsearch.url: "http://100.63.124.194:9200"
However I still get the same error. Is this the correct value or is there something I am missing?
Thanks

Kibana asking for credentials

I set up a Kibana server that is accesing an External ElasticServer Datasource. Nignx is on top, and I access Kibana through it.
On the initial config, I set up the credentials of Kibana using:
sudo htpasswd -c /etc/nginx/htpasswd.users kibanaadmin
Then I was able to access the Kibana Web Console, and see it running. However, the external elasticServer was not configured, so I edited the kibana.yml file to point that external ElasticServer.
elasticsearch.url: "https://bluemix-sandbox-dal-9-portal0.dblayer.com:18671/"
elasticsearch.username: "admin"
elasticsearch.password: "mypass"
When I restarted Kibana, it was able to connect to the elasticsearch server, and in fact it seems that it wrote an entry on the index there.
However, now I am asked for some credentials to get connected to the Kibana Web interface. They are not the kibanaadmin I set up previously, or the ones on elasticsearch database. Which credentials should i use?
Are you sure you're not running Kibana from the wrong ES instance and both Kibana and Nginx are running on the same server. Haven't tried it out personally but then the below links could be handy.
Enabling Kibana Authentication with Nginx
Securing Elasticsearch, Kibana with nginx
Git- Kibana with Nginx Reverse Proxy

Resources