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

Update logstashElasticHosts format #1259

Merged
merged 1 commit into from
Aug 18, 2015

Conversation

briantist
Copy link
Contributor

The original says it uses the same format as tsdbHost, but it doesn't work if you just use host:port. Looking at the code, bosun passes the value(s) here directly to the elastic library which is expecting a URL. Once I used http://host:port I was able to query. The error message given before came directly from the elastic library with a generic error message about there being no hosts available so there was no indication that the configuration format was incorrect.

The original says it uses the same format as tsdbHost, but it doesn't work if you just use host:port. Looking at the code, bosun passes the value(s) here directly to the elastic library which is expecting a URL. Once I used http://host:port I was able to query. The error message given before came directly from the elastic library with a generic error message about there being no hosts available so there was no indication that the configuration format was incorrect.
@kylebrandt
Copy link
Member

I think is already done? someone just needs to regenerate the config? @captncraig can your write how that is done in the developing md?

@captncraig
Copy link
Contributor

What config? Do you mean publishing the docs?

@kylebrandt
Copy link
Member

@captncraig Yes, sorry publishing the docs... so much cold medicine...

captncraig pushed a commit that referenced this pull request Aug 18, 2015
Update logstashElasticHosts format
@captncraig captncraig merged commit 13f1b98 into bosun-monitor:master Aug 18, 2015
@briantist briantist deleted the patch-1 branch August 18, 2015 21:33
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

Successfully merging this pull request may close these issues.

3 participants