Hi,
Just wanted to drop a note that we just release Marvel 1.0.2 which contains
a fix for this.
See http://www.elasticsearch.org/guide/en/marvel/current/#_change_list .
Cheers,
Boaz
On Friday, January 31, 2014 3:23:33 PM UTC+1, Sean Gallagher wrote:
>
> Thanks for reporting this issue! I've s
Thanks for reporting this issue! I've submitted the issue to the internal
repo and the team will take care of it. Keep 'em coming!
On Tuesday, January 28, 2014 10:45:04 AM UTC-5, J. Schulz wrote:
>
> Hi,
>
> I have Nginx configured as reverse proxy to access elasticsearch over
> https + auth b
Glad to see this has been reported already. I ran into the exact same
problem and figured out the same fix too. It would be great if Marvel (and
Kibana actually does the same thing I believe) could modify the supplied
config.js to use window.location.protocol instead of assuming "http://"; all
Understood. :) Can't quite parse twitterspeak early in the morning. It was
interesting seeing a post about Marvel and then immediately someone on the
mailing list asking a question. Wow, that was fast.
For those that missed the news:
http://www.elasticsearch.com/blog/introducing-elasticsearch-marv
You wrote: "I am assuming that the elasticsearch team has Marvel as a
private repo, which means you can't post issues."
I just wanted to show you that I already searched for a place where to
report "bugs" for Marvel and ask Shay on Twitter.
Is it clear now? Have a nice day :-)
--
You received
Not sure what you are trying to accomplish by applying Twitter conventions
on a mailing list. :)
Shay has not been on the mailing list in a long time. Eventually someone
from elasticsearch will read your email.
--
Ivan
On Tue, Jan 28, 2014 at 7:54 AM, J. Schulz wrote:
> I know ;-)
>
> @kimch
I know ;-)
@kimchy where to report bugs? On
http://github.com/elasticsearch/elasticsearch …?
@bloonix for now, best place is the google group:
https://groups.google.com/forum/#!forum/elasticsearch …
Am Dienstag, 28. Januar 2014 16:51:39 UTC+1 schrieb Ivan Brusic:
>
> Marvel was just announced
Marvel was just announced today (to me at least), and there already is a
question/issue? :) Let us know how it is working out.
I am assuming that the elasticsearch team has Marvel as a private repo,
which means you can't post issues.
--
Ivan
On Tue, Jan 28, 2014 at 7:45 AM, J. Schulz wrote:
Hi,
I have Nginx configured as reverse proxy to access elasticsearch over https
+ auth basic. As example
Unfortunately Marvel tries to connect to http://hostname/.
The affected code line is in
/usr/share/elasticsearch/plugins/marvel/_site/kibana/config.js
elasticsearch: "http://"+window.locat
Hi,
I have Nginx configured as reverse proxy to access elasticsearch over https
+ auth basic. As example
Unfortunately Marvel tries to connect to http://hostname/.
The affected code line is in
/usr/share/elasticsearch/plugins/marvel/_site/kibana/config.js
elasticsearch: "https://"+window.loca
10 matches
Mail list logo
