search

ElasticHQ / elasticsearch-HQ

Monitoring and Management Web Application for ElasticSearch instances and clusters.
http://www.elastichq.org
Other
4.96k stars 528 forks source link

Metrics graphs not drawing #506

Open sdesse opened 4 years ago

sdesse commented 4 years ago

General information

Issue Description

I run elasticsearchHQ behind a reverse proxy.

The app is running on a monitoring host http://monitoringhost:4000 on the internal network and it's published by a reverse proxy on Internet under the URL: https://proxy/no-access/elastichq/

The application is working fine but the the metrics graphs are not drawing.

It seems that when pooling the data the path is not reflected in the calls: Calls are: https://proxy/socket.io/?EIO=3&transport=polling&t=MxksoOM Instead of https://proxy/no-access/elastichq/socket.io/?EIO=3&transport=polling&t=MxksoOM

By entering the correct path (I did manually) the data can be retreived, it seem to be a client side issue only. I'm not a develloper and could not find where in the code this URL is called and where to add the path to the URL. I hope you can help fixing this.

Source Code / Logs

See screenshots.

Be Patient

Thanks for all your efforts.

sdesse commented 4 years ago

Inkedelastichq_LI

ghost commented 4 years ago

I have the same issue still on version 3.5.12

sdesse commented 4 years ago

Yes, I have upgraded to the latest hoping that it would be solved but not.

I'm ready to pay a little to get this fixed and few other cutomizations but not sure how to get this organised. If any suggestions please let me know.

sdesse commented 3 years ago

This is still no working (3.5.12).

I tried to see if I can fix this on my end with the reverse proxy but no luck. The setup is:

Web Client -> Internet -> mod_proxy -> ElasticHQ -> elasticcsearch cluster

In the mod_proxy conf: ProxyPass "/elastichq/" "http://127.0.0.1:5000/" ProxyPassReverse "/elastichq/" "http://127.0.0.1:5000/"

All works well except graphs.

I wish we could get this fixed and I am available for a debug session if it can help. I even offered to pay for this fix and few other improvements as I don't code myself.

Hope this gets addressed in 2021, thanks!

autokilla47 commented 1 year ago

April 2023 still...