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

Zipkin + Elasticsearch (ELK) not create index #2218

Closed
blenolopes opened this issue Oct 24, 2018 · 4 comments
Closed

Zipkin + Elasticsearch (ELK) not create index #2218

blenolopes opened this issue Oct 24, 2018 · 4 comments
Labels
elasticsearch Elasticsearch storage component question

Comments

@blenolopes
Copy link

blenolopes commented Oct 24, 2018

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).

kibana-index-zipkin

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:

java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)

Zipkin startup:

java -DSTORAGE_TYPE=elasticsearch -DES_HOSTS=http://localhost:9200 -jar /opt/zipkin.io/bin/zipkin.jar

Error log in Elasticsearch:

[2018-10-24T11:31:59,933][WARN ][o.e.d.i.m.MapperService  ] Setting index.mapper.dynamic is deprecated since indices may not have more than one type anymore.
[2018-10-24T11:31:59,936][WARN ][o.e.d.i.m.MapperService  ] [_default_] mapping is deprecated since it is not useful anymore now that indexes cannot have more than one type
[2018-10-24T11:31:59,954][WARN ][o.e.d.i.m.MapperService  ] Setting index.mapper.dynamic is deprecated since indices may not have more than one type anymore.
[2018-10-24T11:32:00,033][WARN ][o.e.d.c.m.MetaDataCreateIndexService] index or alias name [zipkin:span-2018-10-24] containing ':' is deprecated and will not be supported in Elasticsearch 7.0+
[2018-10-24T11:32:00,245][WARN ][o.e.d.i.m.MapperService  ] Setting index.mapper.dynamic is deprecated since indices may not have more than one type anymore.
@remd
Copy link

remd commented Oct 24, 2018

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:

[2018-10-24T11:32:00,033][WARN ][o.e.d.c.m.MetaDataCreateIndexService] index or alias name [zipkin:span-2018-10-24] containing ':' is deprecated and will not be supported in Elasticsearch 7.0+

Can you query Elasticsearch directly and check if the indices appear in the list or not?

GET _cat/indices/*zipkin*?s=index

@shakuzen shakuzen added elasticsearch Elasticsearch storage component question labels Oct 25, 2018
@codefromthecrypt
Copy link
Member

codefromthecrypt commented Oct 25, 2018 via email

@codefromthecrypt
Copy link
Member

opened an issue on the colon bomb #2219

@blenolopes
Copy link
Author

opened an issue on the colon bomb #2219

Tks adriancole, I'll go there!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
elasticsearch Elasticsearch storage component question
Projects
None yet
Development

No branches or pull requests

4 participants