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

Multiple Targets: No Arrows #7

Open
Amorik opened this issue May 25, 2017 · 6 comments
Open

Multiple Targets: No Arrows #7

Amorik opened this issue May 25, 2017 · 6 comments

Comments

@Amorik
Copy link

Amorik commented May 25, 2017

Hello,

I've been playing with this plugin for a little bit. It seems that when using multiple targets arrows are no longer displayed between the origins and the targets. Is this intentional?

Thanks

~Regards

@xarkes
Copy link
Contributor

xarkes commented May 27, 2017

Hi,
This is not intentional, could you please add a screenshot and check your javascripts logs ? (And paste if any warning/error)
Thanks

@Amorik
Copy link
Author

Amorik commented May 29, 2017

Hi,

Screenshot below. Not sure what logs to check specifically, but i do not see anything in the kibana.log file. On that note, I've just realized I have posted in the wrong repository. I should move this to elastickent fork as I'm using his version for use with 5.4 of Kibana/ES. My apologies.

image

@xarkes
Copy link
Contributor

xarkes commented May 29, 2017

His version will be merged soon or later so I don't think there is any problem posting your issue here.
I meant javascript logs. Just open the map and right clic -> inspect in your web browser, then in the javascript console you should see some warnings/errors.

@Amorik
Copy link
Author

Amorik commented May 29, 2017

Not sure how to copy and paste from that console atm. Below is the screenshot of the console.

There is only one error message that repeats as the map refreshes with new events: "TypeError: Cannot read property 'lat' of undefined".

My ES cluster has no security on it and the query is restricted to only match entries that have a geo-location set. If its not ES then its possible that my target geohash might be causing the problem; it is as follows:
{"loc1":[45.416667,-75.7], "loc2":[37.771,-122.41]}

perhaps this is related to issue #6?

image

@xarkes
Copy link
Contributor

xarkes commented May 29, 2017

Yes looks like related to the issue. Try to follow the indications in my last comment on this issue

@jvoisin
Copy link

jvoisin commented Jul 19, 2017

@Amorik is this fixed on your side?

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

3 participants