-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Zipkin + Elasticsearch (ELK) not create index #2218
Comments
The screenshot you included is showing the Kibana management page for creating index patterns, not the indices themselves. Furthermore, the entries from the deprecation log you have included seem to imply the index creation is working:
Can you query Elasticsearch directly and check if the indices appear in the list or not?
|
ps oh boy on that colon thing.. let's raise a new issue to track this as
this will be disruptive (second major time something like this in index
expression for us. first was having to put the type name in in the first
place.)
|
opened an issue on the colon bomb #2219 |
Tks adriancole, I'll go there! |
Hi everyone!
I have "ELK" (6.4.2) working perfectly with filebeat, metricbeat, packetbeat and winlogbeat in CentOS 7 x86_64 (Kernel 3.10.0-862.11.6.el7.x86_64).
I'm trying to integrate zipkin + elk (see https://logz.io/blog/zipkin-elk/), but Elasticsearch does not create indices with Kibana.
When trying to create the indices in Kibana, the process does not end. (Follow logs below).
I suspect the zipkin connection drivers are not compatible with elk 6.4.2. Has anyone had the same problem and has a "light at the end of the tunnel"?
Tks for all!
Java version:
Zipkin startup:
Error log in Elasticsearch:
The text was updated successfully, but these errors were encountered: