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
Support connecting to multiple versions elasticsearch at runtime [beautified version of PR 2260] #2316
Conversation
a9aa1f4
to
fc03c9d
Compare
Quick tests against v5 seem to behave correctly. |
Hmmm... I seem to be getting:
That just me? Did not get that on the previous PR. Edit: Seems to happen when I enable the AnnotateConf - maybe that was the case in the previous one as well. |
fc03c9d
to
2aed2ee
Compare
@kylebrandt Sorry, it was actually a bug in conf/system_elastic*.go files. I have pushed a fix: fdf3940 Commits in this PR have been reset too. |
Can you reword the first commit to something like:
Then rebase and merge time :-) |
2aed2ee
to
0400704
Compare
…t runtime - Elastic configuration in the system configuration now *requires* that Version be specified or will fail to start. - Bump version to 0.8.0. - Supported versions are: 2.x, 5.x, 6.x.
For supporting multiple versions of elasticsearch at runtime.
0400704
to
6aec5dd
Compare
@kylebrandt Thanks, the new message is better. I tweak it a little bit. Hope that's ok. |
Getting panics on this, not quite sure what it is yet ... "reflect: call with two few arguments" ... I wonder if maybe it is something to do with the prefix but not sure yet |
I will have a look at the prefix key.. |
So far I am also only able to trigger it when running my alerts on a
schedule, and not via the Rule Editor page. I'm not sure if that is the a
difference between the two, or if I just have not found the particular
alert causing the panic yet.
…On Tue, Sep 25, 2018 at 9:48 AM, Pradeep Mishra ***@***.***> wrote:
I will have a look at the prefix key..
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2316 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABnT0HUd3IanmqMgiip8zNfyWwEcW-Kaks5uejQkgaJpZM4W270x>
.
|
@kylebrandt is there any stack trace? Not really sure what's going on. |
|
@kylebrandt same here did run a couple of -Thanks |
got it.... will push to master |
Panic fixed in d400f79 , just a left over argument from the miniprofiler refactor (when it was moved the the State object) |
@kylebrandt Sorry for that. I relied on go build for the miniprofiler refactor that's why it wasn't caught. Thanks. |
@bom-d-van No apologies needed! Really appreciate your work here, this will make ES upgrade path so much better for many people, including at my company :P |
With this patch bosun could connect to elasticsearch servers with different versions. Supported version are: 2.x, 5.x, 6.x. This is a breaking change, requiring users to update their configuration files to explicitly specify elasticsearch version with 2, 5, or 6, otherwise it would just panic (fail fast).
No compile and test errors on my machine, but I haven't test it against real elastic search servers. Publish it here to check out the community's opinions and the possibility of merging onto master. :)
Relevant tickets: #2240, #1982
Related PR: #2260