Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kibana 3 talks directly to Elasticsearch from the browser #240

Closed
vasanthakumarr opened this issue Jul 20, 2013 · 6 comments
Closed

Kibana 3 talks directly to Elasticsearch from the browser #240

vasanthakumarr opened this issue Jul 20, 2013 · 6 comments

Comments

@vasanthakumarr
Copy link

error
Hi to All,

The Kibana 3 not talking directly to Elasticsearch from my browser...I have copied the kibana folder in my web apps folder in web server (Apache Tomcat 6) and configures my config.js as
var config = new Settings(
{
// By default this will attempt to reach ES at the same host you have
// elasticsearch installed on. You probably want to set it to the FQDN of your
// elasticsearch host
//elasticsearch: "http://"+window.location.hostname+":9200",
elasticsearch: 'http://localhost:9200',
kibana_index: "kibana-int",
modules: ['histogram','map','pie','table','filtering',
'timepicker','text','fields','hits','dashcontrol',
'column','derivequeries','trends','bettermap','query'],
}
);

now i run the webserver and elasticsearch server
In browser i mentioned http://localhost:8081/kibana/#/dashboard and my result is
Oops! IndexMissingException[[logstash-*] missing] ....Why this error coming,if my kibana directly talking to my elastic search and more over in dashboard elastic search option is not working...

I have enquired regd the above error in this hub i am not able to get what i am expecting ?

I hope my requirements are clear if not i am ready explain explain..Kindly provide me a solution on this....

Pls find the attachment for your reference
es_server tomcat_server

@caspergasper
Copy link

Do you have any indexes beginning with logstash- in es?
On 20 Jul 2013 08:11, "vasanthakumarr" notifications@github.com wrote:

Hi to All,

The Kibana 3 not talking directly to Elasticsearch from my browser...I
have copied the kibana folder in my web apps folder in web server (Apache
Tomcat 6) and configures my config.js as
var config = new Settings(
{
// By default this will attempt to reach ES at the same host you have
// elasticsearch installed on. You probably want to set it to the FQDN of
your
// elasticsearch host
//elasticsearch: "http://"+window.location.hostname+":9200",

elasticsearch: 'http://localhost:9200',
kibana_index: "kibana-int",
modules: ['histogram','map','pie','table','filtering',
'timepicker','text','fields','hits','dashcontrol',
'column','derivequeries','trends','bettermap','query'],
}
);

now i run the webserver and elasticsearch server
In browser i mentioned http://localhost:8081/kibana/#/dashboard and my
result is
Oops! IndexMissingException[[logstash-*] missing] ....Why this error
coming,if my kibana directly talking to my elastic search and more over in
dashboard elastic search option is not working...

I have enquired regd the above error in this hub i am not able to get what
i am expecting ?

I hope my requirements are clear if not i am ready explain explain..Kindly
provide me a solution on this....


Reply to this email directly or view it on GitHubhttps://github.com//issues/240
.

@vasanthakumarr
Copy link
Author

No i don't have anything like that in my ES server.....

@htplbc
Copy link

htplbc commented Jul 20, 2013

Loaded up the latest 3.0.0 milestone 2 release. I'm having the same issue. I pulled up Fiddler to see what was going on. As you can see Kibana tries to directly access elasticsearch on 9200

image

@htplbc
Copy link

htplbc commented Jul 20, 2013

Ok my issue was fixed my changing the port from 9200 to 80 in the config.js since I'm using the nginx proxy. Disregard. Thanks and it looks great!

@vasanthakumarr
Copy link
Author

Hi i resolved the above issue can u give solution for this error
Uploading timestamp.JPG . . .

"error": "FacetPhaseExecutionException[Facet [0]: (key) field [@timestamp] not found]"

@rashidkpc
Copy link
Contributor

It would appear you do not have an @timestamp field, which is what you currently have configured for the histogram. Note that kibana ships configured for logstash by default. As I have no way of telling what sort of data you would have, I can not predict the fields you would want to use.

faxm0dem pushed a commit to ccin2p3/kibana that referenced this issue Feb 17, 2014
In case getnameinfo() fails to resolve an address, it automatically returns
the numeric IP address without setting an error condition, which messes up
the logic in resolve_sockaddr() and causes the IP address to be truncated if
use_fqdn() is set to no.  This patch instructs getnameinfo() to return
failure instead by passing NI_NAMEREQD in flags.

References: bugzilla elastic#240
Signed-off-by: Balazs Scheidler <bazsi@balabit.hu>
faxm0dem pushed a commit to ccin2p3/kibana that referenced this issue Feb 17, 2014
In case getnameinfo() fails to resolve an address, it automatically returns
the numeric IP address without setting an error condition, which messes up
the logic in resolve_sockaddr() and causes the IP address to be truncated if
use_fqdn() is set to no.  This patch instructs getnameinfo() to return
failure instead by passing NI_NAMEREQD in flags.

References: bugzilla elastic#240
Signed-off-by: Balazs Scheidler <bazsi@balabit.hu>
harper-carroll pushed a commit to harper-carroll/kibana that referenced this issue Jul 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants