search

ElasticHQ / elasticsearch-HQ

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

metrics graph are empty v3.4.1 #426

Open chitenderkumar opened 6 years ago

chitenderkumar commented 6 years ago

General information

Issue Description

when we are trying to access the metrics graphs of a cluster. metrics graphs displayed empty.

kindly support us here, to make it work.

royrusso commented 6 years ago

Anything in logs?

MHi0 commented 6 years ago

Hi Roy, I am facing the same issue on the following platform:

General information OS Platform and Distribution : CentOS 7 ElasticHQ Version: V3.4.1 Elasticsearch Version: 5.6.11 Python version: 3.6 Browser Vendor and Version (if applicable): Chrome and IE

Log is attached.

elastichq_metrics_graph_failure.txt

sdesse commented 6 years ago

Hello, Same issue with Debian.

elasticHQ is installed on a machine inside our network and published through a reverse proxy. I can see that the browser is trying to load a page that does not exist and gets a 404: https://oursite/socket.io/?EIO=3&transport=polling&t=MRoAXOo

The ElasticHQ publication URL is the following: https://oursite/somepath/elastichq/

OS Platform and Distribution : Debian 8 ElasticHQ Version: V3.4.1 Elasticsearch Version: 6.4.2 Python version: 3.4.2 Browser Vendor and Version: Chrome and IE

I don't see the index to store the data in elastic either. Thanks

royrusso commented 6 years ago

... so you don't see the .elastichq index created? Does the main dashboard have data on it?

sdesse commented 6 years ago

Hello, The .elastichq index is here and the application is working.

I have attached the screenshot: elastichq

Other strange behaviors include no auto-refresh and no persistence of the node list sort order and list size.

This is the content of the .elastichq index: { "_index" : ".elastichq", "_type" : "data", "_id" : "hqsettings", "_score" : 1.0, "_source" : { "index_name" : ".elastichq", "historic_days_to_store" : 7, "doc_type" : "data", "websocket_interval" : 5, "historic_poll_interval" : 300, "store_metrics" : true, "doc_id" : "hqsettings", "version" : 1 }

royrusso commented 6 years ago

So the metrics (websocket) approach is failing then. Did you deploy using docker or ?

sdesse commented 6 years ago

just duplicated the git repo in a directory, started the service and I have apache on the same host that publish the app

royrusso commented 6 years ago

Hmm... is Apache acting as a reverse proxy to ES?

sdesse commented 6 years ago

yes https://oursite/somepath/elastic/

royrusso commented 6 years ago

Ok. Let me see if I can reproduce. I vaguely recall similar issue before with reverse proxies and HQ Websockets.

royrusso commented 6 years ago

BTW, when you go to the metrics section, can you attach the log to this ticket? Just the part when you land on the metrics section. I need to see what the calls look like.

Make sure to cleanse anything you don't want public in the log.

sdesse commented 6 years ago

If I click the Metrics button there is no logs in the elasticHQ/application.log but if I load other pages there are. Only thing I get is this: capture

https://oursite/socket.io/?EIO=3&transport=polling&t=MRoAXOo

dbapramod882 commented 5 years ago

Is this fixed.

royrusso commented 5 years ago

Should be fixed in develop. Next release should be soon after the ui issues are resolved. Upgrading the socket related libs seems to have fixed this.