repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
openzipkinzipkin | ci remove travis from all the repos | Enhancement | we once use travis to test arm64 and s390x architecture however it have be three year since any build happen because they move to a billing model and didn t reclassify we as open source same happen with docker hub iirc rather than pretend we be test we should remove all trace of travis that arm64 isn t currently test anywhere be a half truth nowadays because mac silicon ad hoc cover that in any case alternative include emulation could be setup independently through gha as I have see do in other project include one I maintain |
openzipkinzipkin | zipkin v3 the more maintenance friendly version | Enhancement | feature hi back again for a while my company tetrate be sponsor some of my time to help restore zipkin to a maintainable state notably in a way that doesn t break schemas and have more straightforward path to cve update and whatnot this include primary the following which would be address in separate issue or prs and tick off when do change base docker image to not be alpine change the elasticsearch approach to use the normal sdk rationale as year have pass most possibly all of the core maintainer do not run zipkin site anymore this place people in a bad position of merge change out of duty not need certain key area have have neglect even when community member raise prs on they we need to convert the maintainer team to site again and remove hurdle I would conject be a pragmatic way to optimize base layer to not use alpine while I don t have a specific base layer to suggest I think the time since we choose alpine and now there be many more choice of base layer that be small and support java well than alpine do by change base layer it be true we may increase the base image and break emotional threshold like 30 100 mb all in this could result in some pointing like wow look how big java be etc so we have to be grow up and be ok with that kind of concern the conjected value be that by switch key aspect of our base layer include ssl and java setup be more commoditize those who use it will have an easy time with cve maintenance because we don t run into issue that need to be resolve sometimes by alpine themselves this tune for a new set of maintainer site owner who maybe never have a concern like this in the first place elasticsearch driver change many issue have accumulate around elasticsearch support and while our custom driver directly integrate with armeria be more performant and have less dependency it have prove to have a couple issue one be that people have less experience with how to update it another be that reviewer have opt out of merge fix for fear of break thing that change be integrate test in ci isn t the point in general there be both technical and cultural reason this be no long a good match a pragmatic way out be to take the con of elasticsearch s sdk include any bloat or compatibility reduction that cause and performance reduction the conjecture be that if we use the normal driver site owner who be not yet maintainer can become maintainer as well ask es expert for advice in directly applicable way in other word we become less reliant on historical people like anuraaga minwoox and myself for what seem to be a very common concern of es upgrade maintenance example scenario an expected result be that the zipkin v3 release have compatibility with the same schema as v2 have limit to any constraint add by the default elasticsearch client the docker image which be optional as some layer their own likely be an ubuntu slim distribution which be in all likelihood large the exec jar be both large due to the es client dependency tree however all the artifact can use late elasticsearch version backend zipkin v3 be effectively center on this change of es support and that in order to do that we to rewrite that component everything else be the same prior art zipkin as a skywalking extension most notably this be an alternative to the v3 informally introduce in this pr which be to switch zipkin to be effectively a skywalking extension in hindsight that require more discussion and stake with end user vs historical admin notably it break all the schema and would put patch duty requirement on skywalke which be unlike norm of zipkin which have a history of limited to no dependence on other project except notably armeria in any case this can restart in the contrib org like kafka if desire but I would caution about make core change here that only serve this goal at least until zipkin be stable again effectively this issue re own version 3 for continuity and give time for the community to refocus on compatability and potentially a new set of site own committer later that team can decide if work with es be a goal vs change to zipkin be a skywalke dependent ecosystem regardless we thank the skywalking team for interesting alternative to the maintenance problem and hope to stay friend copying of folk notably ping folk who may not have be active recently but should know about this idea I will in parallel start re acclimate with java etc to hit the ground run next monday but yeah if there s a swell of folk say please don t do this stuff I ll trash any wip I have timeboxe the next two week to sort this out docker image our base image be originally create by abesto and then anuraaga and I have a hand in its recent incarnation llinder though deserve mountain of credit for keep it up to date these last year this plan swap it out for something lean but ubuntu not alpine elasticsearch anuraaga minwoox and I work at length on the current es client which use to be okhttp zeagord also have a hand in this and thank llinder for recent maintenance xeraa give a lot of insight over the year as well this plan go to the normal java sdk and end the custom one while retain all the integration test that we can pass with it likely all except thing sensitive to old es version v3 be for skywalke jcchavezs champion the initiative lead by skywalke team mrproliu wu sheng and I think hanahmily to make zipkin a skywalking extension core server use skywalke and while there be schema break manifest the same apis and lens ui basvanbeek shakuzen and anuraaga possibly jeqo be notify about this work and may have strong feeling about an alternative I want to ping they directly rather than walk around this topic historical admin this also dance on the topic of historical admin of zipkin no long be site zipkin s culture be define by its majority be site owner at one point only I be a non site owner while I will raise another issue about this dillemma I ll tag the list openzipkin core meanwhile so folk can start think about this in the issue I raise it will really be about try to harness non vendor site owner again so that stakeful decision lead the way as it once do |
openzipkinzipkin | update documentation and remove unesessary configuration | Enhancement | feature of zipkin v3 have be almost develop so this pull request be intend for update the documentation and remove unnecessary configuration item |
openzipkinzipkin | benchmark throw exception always scope with actuatecollectormetric fortransport | Bug | describe the bug I be try to run the jmh benchmark in benchmark directory when I execute it I get java lang illegalstateexception always scope with actuatecollectormetric fortransport at zipkin2 server internal micrometercollectormetric checkscope micrometercollectormetric java 141 at zipkin2 server internal micrometercollectormetric incrementbyte micrometercollectormetric java 128 at zipkin2 collector metricsbenchmark incrementbyte metricsbenchmark java 82 at zipkin2 collector metricsbenchmark incrementbyte longspan actuate metricsbenchmark java 58 at zipkin2 collector jmh generate metricsbenchmark incrementbyte longspan actuate jmhtest incrementbyte longspan actuate avgt jmhstub metricsbenchmark incrementbyte longspan actuate jmhtest java 186 at zipkin2 collector jmh generate metricsbenchmark incrementbyte longspan actuate jmhtest incrementbyte longspan actuate averagetime metricsbenchmark incrementbyte longspan actuate jmhtest java 150 at java base jdk internal reflect nativemethodaccessorimpl invoke0 native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java 62 at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java 43 at java base java lang reflect method invoke method java 566 at org openjdk jmh runner benchmarkhandler benchmarktask call benchmarkhandler java 453 at org openjdk jmh runner benchmarkhandler benchmarktask call benchmarkhandler java 437 at java base java util concurrent futuretask run futuretask java 264 at java base java util concurrent executors runnableadapter call executor java 515 at java base java util concurrent futuretask run futuretask java 264 at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java 1128 at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java 628 at java base java lang thread run thread java 829 step to reproduce step to reproduce the behavior simply run java jar target benchmark jar inside the benchmark directory expect behaviour no exception run benchmark I m happy to work on a fix but at this point I would appreciate a pointer whether this be a configuration issue or be the test just break |
openzipkinzipkin | sync skywalke upstream version and reduce cassandra storage size | Bug | 1 fix jdbc relate datasource query error bug from skywalke 2 reduce the unnecessary table in the cassandra |
openzipkinzipkin | support collect trace through grpc | Enhancement | support collect trace datum through the grpc protocol as declare in the v2 server grpc collector experimental |
openzipkinzipkin | enhance the query performance and storage size of the cassandra storage in v3 server | Enhancement | 1 improve collect throughput change the synchronous writing of batch datum synchronization to asynchronous writing 2 reduce unnecessary field reduce unnecessary field storage to reduce storage space usage 3 query optimization split the original query method into multiple file so that each query can be optimize well |
openzipkinzipkin | upgrade active mq to at least 5 16 7 to remediate cve 2023 46604 | Bug | in our vulnerability scan zipkin be get flag for cve 2023 46604 due to the presence of activemq 5 16 3 can the activemq to be upgrade to atleast 5 16 7 to remediate this |
openzipkinzipkin | upgrade snappy java to atleast 1 1 10 4 to remediate cve 2023 43642 | Bug | in our vulnerability scan zipkin be get flag for cve 2023 43642 due to the presence of snappy java 1 1 10 3 can the snappy java to be upgrade to atleast 1 1 10 4 to remediate this |
openzipkinzipkin | reduce the execute time of ci | Enhancement | currently the ci time for version v3 be quite long this pr be use to skip the skywalking relate ci test |
openzipkinzipkin | support collect otlp trace in v3 server | Enhancement | support receive otlp trace protocol datum base on grpc and convert it to the format of zipkin span for storage and query |
openzipkinzipkin | support search enable configuration | Enhancement | support to configuration span be searchable if it be not searchable no table would be create except for span and trace datum can only be query by traceid |
openzipkinzipkin | support update the default log level when startup | Enhancement | support add property when start the server to modify the log level for example java dlog level debug jar zipkin jar |
openzipkinzipkin | fix annotation scan not work in v3 server | Bug | due to zipkin package all dependency into a single jar skywalke s previous annotation scan logic within the core do not support scan file within sub jar therefore we ve replace it with use the classgraph module to achieve the original annotation scan logic |
openzipkinzipkin | when there be too many span ui rendering fail | Bug | front end render fail even cause the browser to freeze |
openzipkinzipkin | zipkin 2 24 3 not support elasticsearch8 x | Bug | hello I m currently use elasticsearch 8 x and when consume kafka and write to elasticsearch with zipkin 2 24 3 I encounter an error indicate that it do not support version 7 and above |
openzipkinzipkin | do zipkin 2 24 3 support java17 and elasticsearch8 x | Enhancement | do zipkin 2 24 3 support java17 and elasticsearch8 x |
openzipkinzipkin | cve 2023 38493 on direct dependency com linecorp armeria armeria | Bug | describe the bug in our vulnerability scan zipkin be get flag for cve 2023 38493 due to the direct dependency on com linecorp armeria armeria can com linecorp armeria armeria be upgrade to 1 24 3 at least |
openzipkinzipkin | release note for 2 24 2 | Bug | release note for 2 24 2 be miss from |
openzipkinzipkin | zipkin 2 24 2 mysql connector j 8 0 32 springboot 2 7 12 runtime error | Bug | describe the bug what s wrong |
openzipkinzipkin | docker image not work on arm64 when elasticsearch storage be use | Bug | describe the bug when start the default docker image on an arm mac with the elasticsearch storage enble the jvm segfault a fatal error have be detect by the java runtime environment sigsegv 0xb at pc 0x0000000000020820 pid 1 tid 7 jre version openjdk runtime environment 17 0 5 8 build 17 0 5 8 alpine r2 java vm openjdk 64 bit server vm 17 0 5 8 alpine r2 mixed mode tiere compress oop compress class ptrs g1 gc linux aarch64 problematic frame c 0x0000000000020820 core dump will be write default location zipkin core max size 1000 kb to ensure a full core dump try ulimit c unlimited before start java again if you would like to submit a bug report please visit the crash happen outside the java virtual machine in native code see problematic frame for where to report the bug for size reason I ve move the entire dump to a gist step to reproduce on an arm64 mac with docker instal run the follow command docker run rm e storage type elasticsearch e es host e es index zipkin openzipkin zipkin 2 24 1 which crash directly with the follow output oo oooo oooooo oooooooo oooooooooo oooooooooooo ooooooo ooooooo oooooo ooooooo oooooo ooooooo oooooo o o oooooo oooooo oo oo oooooo ooooooo oooo oooo ooooooo oooooo ooooo ooooo ooooooo oooooo oooooo oooooo ooooooo oooooooo oo oo oooooooo ooooooooooooo oo oo ooooooooooooo oooooooooooo oooooooooooo oooooooo oooooooo oooo oooo version 2 24 1 commit 5e3402a a fatal error have be detect by the java runtime environment sigsegv 0xb at pc 0x0000000000020820 pid 1 tid 7 jre version openjdk runtime environment 17 0 5 8 build 17 0 5 8 alpine r2 java vm openjdk 64 bit server vm 17 0 5 8 alpine r2 mixed mode tiere compress oop compress class ptrs g1 gc linux aarch64 problematic frame c 0x0000000000020820 no core dump will be write core dump have be disable to enable core dumping try ulimit c unlimited before start java again an error report file with more information be save as zipkin hs err pid1 log if you would like to submit a bug report please visit the crash happen outside the java virtual machine in native code see problematic frame for where to report the bug on a linux machine the same command boot zipkin just fine on the same mac it also work fine use the follow docker command docker run rm openzipkin zipkin 2 24 1 expect behaviour similar to linux the mac variant boot normally |
openzipkinzipkin | zipkin dependency graph not work with elasticsearch storage | Question | I be start to use zipkin and I have an issue when I run docker compose f docker compose elasticsearch yml up d at docker example and the dependency graph be not display when use elasticsearch but it do work when I use mysql or memory storage could anyone help I please thank you |
openzipkinzipkin | mysql docker image build be break | Bug | describe the bug mysql version use in docker image building process be a broken dependency step 5 6471 step to reproduce step to reproduce the behavior docker file docker test image zipkin mysql dockerfile build bin docker docker build openzipkin zipkin mysql test |
openzipkinzipkin | cassandra docker image build be break | Bug | describe the bug when build cassandra image it s fail when use python step 11 190 step to reproduce step to reproduce the behavior docker file docker test image zipkin cassandra dockerfile build bin docker docker build openzipkin zipkin cassandra test |
openzipkinzipkin | update kafka client to at least 3 4 0 to remediate cve 2023 25194 | Bug | zipkin be get flag in our security scan due to the presence of org apache kafka kafka client which have cve 2023 25194 be there any plan to upgrade kafka client to at least 3 4 0 to get around this |
openzipkinzipkin | can not read property of undefined reading spanid | Bug | when upgrade zipkin from 2 14 to late 2 24 I get the follow error when click the show button on certain trace typeerror can not read property of undefined reading spanid at ao timeline tsx 88 50 at xo react dom production min js 153 146 at ms react dom production min js 261 496 at cl react dom production min js 246 265 at sl react dom production min js 246 194 at s react dom production min js 239 172 at react dom production min js 123 115 at t unstable runwithpriority scheduler production min js 19 467 at gi react dom production min js 122 325 at yi react dom production min js 123 61 image I ve try to debug the code the reason for the problem may be due to the lack of proper error handle image image src component tracepage helper ts line 32 const root span filter span span parentid the root that return be an empty array and I check my datum it just do not have th expect span but it work well on the old ui |
openzipkinzipkin | zipkin be not display all span | Bug | ui display bug not all span be display I m trace the spring cloud dataflow example application with zipkin it be compose of a source a processor and a sink the tracing encompass all three service zipkin however be display only one of those service correctly I be assume that the other service be not trace but after download and upload the trace json from and back to zipkin all three service be display correctly and all three be present in the trace json file this but occur in zipkin version v2 23 18 this be how the trace be display initially in zipkin after download reuploade into zipkin and reload the trace look as follow this be the json of the trace traceid 324c7add82507a94 parentid 324c7add82507a94 i d 5138d85b03ee35ea kind consumer timestamp 1680344729141104 duration 3 localendpoint servicename cost proc ipv4 192 168 0 10 remoteendpoint servicename broker tag channel processusagecost traceid 324c7add82507a94 parentid ba1726a56baf1940 i d 658e13bf9c7d2371 name usagecostprocessor explicit timestamp 1680344729141531 duration 132 localendpoint servicename cost proc ipv4 192 168 0 10 annotation timestamp 1680344729141595 value processor costrecalculate tag callcost 28 900000000000002 datacost 1 7000000000000002 userid user1 traceid 324c7add82507a94 parentid 5138d85b03ee35ea i d ba1726a56baf1940 name handle timestamp 1680344729141273 duration 694 localendpoint servicename cost proc ipv4 192 168 0 10 traceid 324c7add82507a94 i d 324c7add82507a94 timestamp 1680344729141074 localendpoint servicename cost proc ipv4 192 168 0 10 traceid 324c7add82507a94 parentid 658e13bf9c7d2371 i d 8b4376afaa3ed7a6 name usagecostprocessor explicit inner timestamp 1680344729141616 localendpoint servicename cost proc ipv4 192 168 0 10 traceid 324c7add82507a94 parentid 5138d85b03ee35ea i d 5bd5436398cbbd17 kind producer name send timestamp 1680344729142105 duration 65 localendpoint servicename cost proc ipv4 192 168 0 10 remoteendpoint servicename kafka tag channel processusagecost traceid 324c7add82507a94 parentid 99a01bb292764eef i d da05e8d9aadd8300 kind consumer timestamp 1680344729146304 duration 3 localendpoint servicename cost calc ipv4 192 168 0 10 remoteendpoint servicename broker tag channel processusagecost traceid 324c7add82507a94 parentid 34a02a80de973818 i d 243d12c56507f2e1 name usagecostcalculator within timestamp 1680344729146729 duration 50 localendpoint servicename cost calc ipv4 192 168 0 10 annotation timestamp 1680344729146770 value costrecalculate tag callcost 2 8900000000000006 datacost 0 08500000000000002 userid user1 traceid 324c7add82507a94 parentid da05e8d9aadd8300 i d 34a02a80de973818 name handle timestamp 1680344729146463 duration 587 localendpoint servicename cost calc ipv4 192 168 0 10 traceid 324c7add82507a94 parentid da05e8d9aadd8300 i d 1785951dd42c8780 kind producer name send timestamp 1680344729147172 duration 69 localendpoint servicename cost calc ipv4 192 168 0 10 remoteendpoint servicename kafka tag channel processusagecost traceid 324c7add82507a94 parentid c9d8493e0f582de7 i d 057760a5e8f57da7 kind consumer timestamp 1680344729150641 duration 3 localendpoint servicename cost log ipv4 192 168 0 10 remoteendpoint servicename broker tag channel process traceid 324c7add82507a94 parentid 057760a5e8f57da7 i d ba4673b1c91dc30f name handle timestamp 1680344729150842 duration 731 localendpoint servicename cost log ipv4 192 168 0 10 traceid 324c7add82507a94 parentid 1785951dd42c8780 i d c9d8493e0f582de7 timestamp 1680344729150610 localendpoint servicename cost log ipv4 192 168 0 10 traceid 324c7add82507a94 parentid ba4673b1c91dc30f i d 1eec13d3b6ddabdc name usagecostlogger timestamp 1680344729151183 duration 268 localendpoint servicename cost log ipv4 192 168 0 10 tag callcost 2 8900000000000006 datacost 0 08500000000000002 userid user1 step to reproduce step to reproduce the behavior run the scdf application in the follow repository expect behaviour I expect all three service to be display properly without download and re upload |
openzipkinzipkin | replace deprecate set output command with environment file | Enhancement | describe the issue in workflow set output command be deprecate and will be disable soon please upgrade to use environment file for more information see |
openzipkinzipkin | autoscale v2beta1 be remove from kubernete 1 25 | Invalid | please first look at exist issue to see if the feature have be request before if you don t find anything tell we what problem you re try to solve often a solution already exist don t send pull request to implement new feature without first get our support sometimes we leave feature out on purpose to keep the project small feature please update to autoscale v2 rationale why would this feature help other besides I example scenario what kind of use case would benefit from this feature prior art link to prior art more link |
openzipkinzipkin | update netty to 4 1 86 final to remediate cve 2022 41881 | Bug | zipkin be get flag in our security scan due to the presence of io netty netty codec haproxy 4 1 78 final which have cve 2022 41881 be there any plan to upgrade io netty netty codec haproxy to 4 1 86 final to get around this |
openzipkinzipkin | app not communicate with zipkin after enable ssl in zipkin | Question | after enable ssl in zipkin version 2 23 16 with the self sign certificate the application be not send the trace info to zipkin the web application uiapi appear to have start a thread name asyncreporter resttemplatesender of zipkin api v2 span but have fail to stop it this be very likely to create a memory leak stack trace of thread jdk internal misc unsafe park native method java util concurrent lock locksupport parknanos locksupport java 234 java util concurrent lock abstractqueuedsynchronizer conditionobject awaitnanos abstractqueuedsynchronizer java 2123 app zipkin2 reporter byteboundedqueue drainto byteboundedqueue java 81 app zipkin2 reporter asyncreporter boundedasyncreporter flush asyncreporter java 270 app zipkin2 reporter asyncreporter flusher run asyncreporter java 378 java lang thread run thread java 834 |
openzipkinzipkin | zipkin dedendencie for cassandra | Bug | hello be start use zipkin and I guess I ve find a bug where dependency be not properly display when use apache cassandra but it do work when I use mysql or memory storage as follow mysql or memory storage docker compose yml service zipkin container name zipkin image openzipkin zipkin expose 9411 port 9411 9411 environment query port 9411 java opt xms8 g xmx8 g screenshot image cassandra docker compose yml service zipkin container name zipkin image openzipkin zipkin expose 9411 port 9411 9411 environment storage type cassandra3 cassandra contact point localhost 9042 zipkin ui dependency enable true query port 9411 java opt xms8 g xmx8 g cassandra container name cassandra image cassandra 3 11 14 expose 9042 port 9042 9042 screenshot image all service post be work fine and we can check they on find a trace user interface I also have try for environment property zipkin ui dependency enable true but still no success could find anything on zipkin documentation be this a know bug or do I miss some additional configuration thank in advance |
openzipkinzipkin | trace with miss root span be not render correctly in zipkin len | Bug | describe the bug in zipkin lens 2 24 view trace detail where the root span be miss a parentid be refer to a miss span a blank page be render and an error be show in developer tool console an example trace abbreviate look like span with i d ebec1841bdb48ba1 be miss traceid b523777284bbb42aa6304c7a5cd35fd7 parentid ebec1841bdb48ba1 i d 3eca62ab99ac8e84 timestamp 1675053275397814 traceid b523777284bbb42aa6304c7a5cd35fd7 parentid 3eca62ab99ac8e84 i d 7021b3404bd7b9d6 timestamp 1675053275401192 here be the full trace gist in 2 24 this render as follow step to reproduce 1 post a trace to zipkin with one or more span with the root span miss 2 click show to view detail in zipkin lens expect behaviour trace should render correctly even if root span be miss or an error message should be show instead of a blank page in 2 23 this example render correctly as |
openzipkinzipkin | update to zipkin slim image require to fix cve 2022 3996 | Bug | zipkin 2 24 0 contain the follow high severity cve total 2 unknown 0 low 0 medium 0 high 2 critical 0 library vulnerability severity instal version fix version title libcrypto3 cve 2022 3996 high 3 0 7 r0 3 0 7 r2 openssl double locking lead to denial of service libssl3 see or |
openzipkinzipkin | address the case where the root span parentid be not empty | Bug | there may be case where the parentid of the root span be not empty but traceid this pr address that case |
openzipkinzipkin | revamp trace page | Enhancement | this pr will refactor and simplify the process of create the trace tree change the design add minitimeline feature add spantable feature add annotationtooltip feature |
openzipkinzipkin | update alpine for cve 2022 3602 or remove openssl lib from image | Bug | describe the bug current openzipkin container image on docker hub 2 23 19 contain a libcrypto so 3 that appear to be openssl v3 3 and thus subject to cve 2022 3602 this be completely harmless because openjdk do not link to libcrypto and it do not dlopen it when execute zipkin either at least in my test neither snyk nor trivy complain about it in my test another scanner I have access to do flag it even though it s basically harmless it should be update or remove probably by update to a new base alpine contain a fix step to reproduce docker run it rm entrypoint bin sh openzipkin zipkin 2 23 19 c find type f a name libcrypto o name libssl 2 dev null xargs grep openssl 3 lib libcrypto so 3 openssl 3 0 0 lib libcrypto so 3 openssl 3 0 3 expect behaviour either omit openssl lib from the image entirely or update to new alpine contain fix once alpine release one workaround I just delete the libs from my image with an overlay from openzipkin zipkin 2 23 19 for cve 2022 3602 openssl simply delete the openssl lib java doesn t load they in its jce provider and we only run java in this image user root run rm usr lib libcrypto usr lib libssl lib libcrypto lib libssl user zipkin |
openzipkinzipkin | release zipkin with update netty for cve 2022 24823 and cve 2021 43797 | Bug | describe the bug image be flag with cve 2022 24823 and cve 2021 43797 step to reproduce scan the image with azure defender expect behaviour this vulnerability be publish 05 06 2022 and 07 25 2022 should be fix ref netty 4 1 77 or great fix both issue |
openzipkinzipkin | not able to upgrade os package of docker image | Bug | describe the bug when I want to update the os package of the docker image then I receive the follow error error ca certificate bundle 20220614 r2 try to overwrite etc ssl1 1 cert pem own by libcrypto1 1 1 1 1n r0 error ca certificate bundle 20220614 r2 try to overwrite etc ssl1 1 cert own by libcrypto1 1 1 1 1n r0 step to reproduce step to reproduce the behavior 1 create a dockerfile contain the follow sh from openzipkin zipkin 2 23 user root run apk upgrade no cache user zipkin 2 run the docker build command docker build t test expect behaviour the expect behaviour be that the package be upgrade and the docker build do not fail |
openzipkinzipkin | elasticsearch version 5 7 x be support be 8 0 | Bug | openstack zipkin slim not connect with elasticsearch 8 3 0 we be use the docker image form with elastic search 8 0 0 or 8 3 0 zipkin be not able to connect show I error java lang illegalargumentexception elasticsearch version 5 7 x be support be 8 0 at zipkin2 elasticsearch versionspecifictemplate get versionspecifictemplate java 227 at zipkin2 elasticsearch elasticsearchstorage versionspecifictemplate elasticsearchstorage java 356 at zipkin2 elasticsearch elasticsearchstorage doensureindextemplate elasticsearchstorage java 338 at zipkin2 elasticsearch elasticsearchstorage ensureindextemplate elasticsearchstorage java 330 at zipkin2 elasticsearch elasticsearchstorage spanconsumer elasticsearchstorage java 249 at zipkin2 server internal brave zipkinselftracingconfiguration localsender sendspans zipkinselftracingconfiguration java 163 at zipkin2 reporter asyncreporter boundedasyncreporter flush asyncreporter java 299 at zipkin2 reporter asyncreporter flusher run asyncreporter java 378 at zipkin2 server internal brave zipkinselftracingconfiguration 1 run zipkinselftracingconfiguration java 55 at java base java lang thread run unknown source can you please confirm if be there any version to support es 8 3 0 |
openzipkinzipkin | fr support of junit5 engine | Enhancement | feature now zipkin provide zipkin junit module it s very useful in test however it only work with junit4 I hope it can support junit5 too rationale this feature benefit all junit5 user example scenario people who use junit5 and want to use zipkin test module |
openzipkinzipkin | zipkin bundle gson 2 8 6 that have know vulnerability | Bug | describe the bug late be show to depend and to bundle gson that have know vulnerability cve 2022 25647 score 7 5 high step to reproduce check with tool like black duck software it find gson in zipkin 2 23 16 jar zipkin2 internal gson stream expect behaviour please upgrade to gson 2 8 9 or new |
openzipkinzipkin | disable zipkin ui without disable read endpoint | Enhancement | feature add a runtime property that only disable zipkin ui without disable read endpoint rationale currently if you need to disable zipkin ui the only option be to set query enable to false however this disable the http read endpoint if you want to get trace datum use the zipkin read endpoint but you need to disable the ui there be no solution example scenario example scenario can be explain as follow 1 zipkin do not have oauth 2 0 natively integrate therefore oauth 2 0 compliant integration like okta be not possible with zipkin 2 instead of provide user with zipkin ui without oauth 2 0 auth use grafana as grafana have build in okta integration support trace datum be send from line of business application to zipkin use grafana s build in zipkin support to use zipkin as your data source 3 view trace datum from the grafana ui 4 disable zipkin ui to avoid unauthenticated access as you can see from the step above grafana will not be able to retrieve trace datum from zipkin if the zipkin read endpoint be disabled |
openzipkinzipkin | empty trace due to some ui react issue | Bug | trace can not be display due to some ui react issue the issue have be reproduce with both the elasticsearch and mem storage on the late version of zipkin trace be generate by spring boot 2 7 0 and sleuth 3 1 3 business flow a chain of spring boot micro service communicate with each other use kafka grpc etc see the json at the end of the question it seem the last trace be always work so a work trace will be corrupt once a new trace will be available in the ui any link with in flight trace fee free to ask if you need more detail see the stackoverflow post for more detail json screenshot etc |
openzipkinzipkin | java lang noclassdeffounderror com google gson stream jsonreader error when start up zipkin 2 23 16 server | Question | java lang noclassdeffounderror com google gson stream jsonreader at zipkin2 internal jsoncodec jsonreader jsoncodec java 51 class at zipkin2 internal jsoncodec readlist jsoncodec java 143 class at zipkin2 codec spanbytesdecoder 3 decodelist spanbytesdecoder java 123 class at zipkin2 collector collector decodelist collector java 196 class at zipkin2 collector collector acceptspans collector java 186 class at zipkin2 collector collector acceptspans collector java 172 class at zipkin2 collector kafka kafkacollectorworker run kafkacollectorworker java 111 class at zipkin2 collector kafka kafkacollector lazykafkaworker lambda guardfailure 0 kafkacollector java 265 class at java util concurrent threadpoolexecutor runworker threadpoolexecutor java 1149 1 8 0 201 at java util concurrent threadpoolexecutor worker run threadpoolexecutor java 624 1 8 0 201 at java lang thread run thread java 748 1 8 0 201 cause by java lang classnotfoundexception com google gson stream jsonreader at java net urlclassloader findclass urlclassloader java 382 1 8 0 201 at java lang classloader loadclass classloader java 424 1 8 0 201 at sun misc launcher appclassloader loadclass launcher java 349 1 8 0 201 at java lang classloader loadclass classloader java 357 1 8 0 201 11 more |
openzipkinzipkin | zipkin pod not start with elastic 8 2 | Bug | hello I upgrade my elastic cluster to 8 2 and I realize zipkin pod doesn t start the log of the pod show oo oooo oooooo oooooooo oooooooooo oooooooooooo ooooooo ooooooo oooooo ooooooo oooooo ooooooo oooooo o o oooooo oooooo oo oo oooooo ooooooo oooo oooo ooooooo oooooo ooooo ooooo ooooooo oooooo oooooo oooooo ooooooo oooooooo oo oo oooooooo ooooooooooooo oo oo ooooooooooooo oooooooooooo oooooooooooo oooooooo oooooooo oooo oooo power by spring boot v2 1 8 release 2022 06 07 07 40 40 942 info 1 main z s zipkinserver start zipkinserver on zipkin server 858587c464 4rjww with pid 1 zipkin boot inf class start by zipkin in zipkin 2022 06 07 07 40 40 947 info 1 main z s zipkinserver the follow profile be active share 2022 06 07 07 40 43 895 info 1 main c l a c flag com linecorp armeria verboseexception rate limit 10 default 2022 06 07 07 40 43 907 info 1 main c l a c flag com linecorp armeria verbosesocketexception false default 2022 06 07 07 40 43 907 info 1 main c l a c flag com linecorp armeria verboseresponse false default 2022 06 07 07 40 43 947 info 1 main c l a c flag com linecorp armeria useepoll true default 2022 06 07 07 40 44 218 info 1 main c l a c flag com linecorp armeria useopenssl true default 2022 06 07 07 40 44 218 info 1 main c l a c flag com linecorp armeria dumpopensslinfo false default 2022 06 07 07 40 44 220 info 1 main c l a c flag com linecorp armeria maxnumconnection 2147483647 default 2022 06 07 07 40 44 222 info 1 main c l a c flag com linecorp armeria numcommonworker 2 default 2022 06 07 07 40 44 222 info 1 main c l a c flag com linecorp armeria numcommonblockingtaskthread 200 default 2022 06 07 07 40 44 224 info 1 main c l a c flag com linecorp armeria defaultmaxrequestlength 10485760 default 2022 06 07 07 40 44 227 info 1 main c l a c flag com linecorp armeria defaultmaxresponselength 10485760 default 2022 06 07 07 40 44 228 info 1 main c l a c flag com linecorp armeria defaultrequesttimeoutmillis 10000 default 2022 06 07 07 40 44 228 info 1 main c l a c flag com linecorp armeria defaultresponsetimeoutmillis 15000 default 2022 06 07 07 40 44 229 info 1 main c l a c flag com linecorp armeria defaultconnecttimeoutmillis 3200 default 2022 06 07 07 40 44 230 info 1 main c l a c flag com linecorp armeria defaultwritetimeoutmillis 1000 default 2022 06 07 07 40 44 231 info 1 main c l a c flag com linecorp armeria defaultserveridletimeoutmillis 15000 default 2022 06 07 07 40 44 231 info 1 main c l a c flag com linecorp armeria defaultclientidletimeoutmillis 10000 default 2022 06 07 07 40 44 232 info 1 main c l a c flag com linecorp armeria defaulthttp2initialconnectionwindowsize 1048576 default 2022 06 07 07 40 44 232 info 1 main c l a c flag com linecorp armeria defaulthttp2initialstreamwindowsize 1048576 default 2022 06 07 07 40 44 233 info 1 main c l a c flag com linecorp armeria defaulthttp2maxframesize 16384 default 2022 06 07 07 40 44 234 info 1 main c l a c flag com linecorp armeria defaulthttp2maxstreamsperconnection 2147483647 default 2022 06 07 07 40 44 234 info 1 main c l a c flag com linecorp armeria defaulthttp2maxheaderlistsize 8192 default 2022 06 07 07 40 44 235 info 1 main c l a c flag com linecorp armeria defaulthttp1maxinitiallinelength 4096 default 2022 06 07 07 40 44 235 info 1 main c l a c flag com linecorp armeria defaulthttp1maxheadersize 8192 default 2022 06 07 07 40 44 236 info 1 main c l a c flag com linecorp armeria defaulthttp1maxchunksize 8192 default 2022 06 07 07 40 44 236 info 1 main c l a c flag com linecorp armeria defaultusehttp2preface true default 2022 06 07 07 40 44 236 info 1 main c l a c flag com linecorp armeria defaultusehttp1pipelining false default 2022 06 07 07 40 44 237 info 1 main c l a c flag com linecorp armeria defaultbackoffspec exponential 200 10000 jitter 0 2 default 2022 06 07 07 40 44 237 info 1 main c l a c flag com linecorp armeria defaultmaxtotalattempt 10 default 2022 06 07 07 40 44 238 info 1 main c l a c flag com linecorp armeria routecache maximumsize 4096 default 2022 06 07 07 40 44 238 info 1 main c l a c flag com linecorp armeria routedecoratorcache maximumsize 4096 default 2022 06 07 07 40 44 239 info 1 main c l a c flag com linecorp armeria compositeservicecache maximumsize 256 default 2022 06 07 07 40 44 239 info 1 main c l a c flag com linecorp armeria parsedpathcache maximumsize 4096 default 2022 06 07 07 40 44 239 info 1 main c l a c flag com linecorp armeria headervaluecache maximumsize 4096 default 2022 06 07 07 40 44 240 info 1 main c l a c flag com linecorp armeria cachedheader authority scheme method accept encode content type default 2022 06 07 07 40 44 243 info 1 main c l a c flag com linecorp armeria annotatedserviceexceptionverbosity unhandle default 2022 06 07 07 40 44 243 info 1 main c l a c flag use dev epoll 2022 06 07 07 40 44 244 info 1 main c l a c flag use openssl boringssl 0x1010007f 2022 06 07 07 40 45 794 info 1 main c l a s d docstringextractor use com linecorp armeria thrift jsondir meta inf armeria thrift 2022 06 07 07 40 45 836 info 1 main c l a c u systeminfo hostname zipkin server 858587c464 4rjww from proc sys kernel hostname 2022 06 07 07 40 46 242 info 1 oss http 9411 c l a s server serve http at 0 0 0 0 9411 2022 06 07 07 40 46 249 info 1 main c l a s armeriaautoconfiguration armeria server start at port 0 0 0 0 9411 serverport 0 0 0 0 9411 http 2022 06 07 07 40 46 324 info 1 main z s zipkinserver start zipkinserver in 6 653 second jvm run for 9 197 2022 06 07 07 42 43 347 info 1 orker epoll 2 1 c l a i javaversionspecific use the apis optimize for java 9 |
openzipkinzipkin | add support for ppc64le | Enhancement | feature to make the docker image available for ppc64le power arch rationale for knative component we need zipkin on power ppc64le like support add for s390x 3310 example scenario client want to use knative on top of it they can use zipkin |
openzipkinzipkin | cve 2022 22965 spring framework security issue | Bug | security issue raise by spring official organization for detail please refer to the spring official website |
openzipkinzipkin | zipkin connect elasticsearch with password | Bug | describe the bug I run zipkin and elastic official image 7 17 1 when elastic xpack security enable true how how to connect my zipkin to this elastic I can t find the environment |
openzipkinzipkin | helm chart java opt support | Enhancement | there be no possibility to set java opt in helm chart right now we be use elasticsearch as storage type and start zipkin file use hardcode value java opt java opt xms32 m xmx32 m xx exitonoutofmemoryerror in this case feature additional value for java opt handle by helm chart should be support rationale rightnow zipkin take hardcode value that be not work with elasticsearch no more than 100 value can be show in zipkin because of terminate due to java lang outofmemoryerror java heap space example scenario this will help with set up value for java to zipkin be able to show more than 100 result in case of elasticsearch be use |
openzipkinzipkin | secure connection to kafka fail with java lang classnotfoundexception org ietf jgss gssexception | Bug | describe the bug I m try to collect stat from kafka in clonfluent cloud use sasl ssl and the docker image I have the follow kubernete config command java args xms128 m xmx1028 m xx exitonoutofmemoryerror cp boot inf lib dlog4j2 disable jmx true dlogging level zipkin2 debug dzipkin collector kafka override sasl jaas config org apache kafka common security plain plainloginmodule require username xxx password xxx dzipkin collector kafka override security protocol sasl ssl dzipkin collector kafka override sasl mechanism plain org springframework boot loader propertieslauncher env name kafka bootstrap server value pkc l6wr6 europe west2 gcp confluent cloud 9092 name kafka topic value zipkin name collector kafka enable value true much as on gitter step to reproduce start docker image with any sasl protocol expect behaviour I expect the consumer to connect and collect stat actual behaviour the follow stack trace zipkin 74b76bfbd dpz45 ksqldb2 org apache kafka common kafkaexception fail to construct kafka consumer zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka client consumer kafkaconsumer kafkaconsumer java 823 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka client consumer kafkaconsumer kafkaconsumer java 665 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka client consumer kafkaconsumer kafkaconsumer java 646 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka client consumer kafkaconsumer kafkaconsumer java 626 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 at zipkin2 collector kafka kafkacollectorworker run kafkacollectorworker java 69 zipkin collector kafka 2 23 16 jar zipkin 74b76bfbd dpz45 ksqldb2 at zipkin2 collector kafka kafkacollector lazykafkaworker lambda guardfailure 0 kafkacollector java 265 zipkin collector kafka 2 23 16 jar zipkin 74b76bfbd dpz45 ksqldb2 at java util concurrent threadpoolexecutor runworker unknown source zipkin 74b76bfbd dpz45 ksqldb2 at java util concurrent threadpoolexecutor worker run unknown source zipkin 74b76bfbd dpz45 ksqldb2 at java lang thread run unknown source zipkin 74b76bfbd dpz45 ksqldb2 cause by java lang noclassdeffounderror org ietf jgss gssexception zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka common network channelbuilder create channelbuilder java 171 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka common network channelbuilder clientchannelbuilder channelbuilder java 81 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka client clientutil createchannelbuilder clientutil java 105 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka client consumer kafkaconsumer kafkaconsumer java 737 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 8 more zipkin 74b76bfbd dpz45 ksqldb2 cause by java lang classnotfoundexception org ietf jgss gssexception zipkin 74b76bfbd dpz45 ksqldb2 at jdk internal loader builtinclassloader loadclass unknown source zipkin 74b76bfbd dpz45 ksqldb2 at jdk internal loader classloader appclassloader loadclass unknown source zipkin 74b76bfbd dpz45 ksqldb2 at java lang classloader loadclass unknown source zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka common network channelbuilder create channelbuilder java 171 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka common network channelbuilder clientchannelbuilder channelbuilder java 81 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka client clientutil createchannelbuilder clientutil java 105 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 at org apache kafka client consumer kafkaconsumer kafkaconsumer java 737 kafka client 2 8 1 jar zipkin 74b76bfbd dpz45 ksqldb2 8 more |
openzipkinzipkin | contenttoolargeexception maxcontentlength 10485760 | Bug | contenttoolargeexception maxcontentlength 10485760 zipkin version 2 23 16 elasticsearch 7 10 0 4 may 2021 allow specify current max content length when create contenttoolargeexception cat zipkin spring log grep contenttoolargeexception com linecorp armeria common contenttoolargeexception maxcontentlength 10485760 contentlength 16345532 transfer 10491189 at com linecorp armeria common contenttoolargeexceptionbuilder build contenttoolargeexceptionbuilder java 78 com linecorp armeria common contenttoolargeexception maxcontentlength 10485760 contentlength 11470475 transfer 10491189 at com linecorp armeria common contenttoolargeexceptionbuilder build contenttoolargeexceptionbuilder java 78 step to reproduce ui issue zipkin search limit for examle 1300 and last 7 day fail to search internal server error expect behaviour define maxcontentlength zipkin search for examle 1300 and last 7 day |
openzipkinzipkin | table doesn t exist in 2 23 15 | Bug | describe the bug a clear and concise description of what the bug be if you have a solution in mind skip raise an issue and open a pull request instead start zipkin with an already exist cassandra instance with cassandra ensure schema the log indicate the migration be run oo oooo oooooo oooooooo oooooooooo oooooooooooo ooooooo ooooooo oooooo ooooooo oooooo ooooooo oooooo o o oooooo oooooo oo oo oooooo ooooooo oooo oooo ooooooo oooooo ooooo ooooo ooooooo oooooo oooooo oooooo ooooooo oooooooo oo oo oooooooo ooooooooooooo oo oo ooooooooooooo oooooooooooo oooooooooooo oooooooo oooooooo oooo oooo version 2 23 15 commit 63365bb 2021 12 19 20 15 59 014 info 1 oss http 9411 c l a s server serve http at 0 0 0 0 0 0 0 0 0 9411 2021 12 19 20 16 39 527 info 1 cke task 1 1 z s c schema instal schema zipkin2 schema cql for keyspace zipkin2 2021 12 19 20 16 45 237 info 1 cke task 1 1 z s c schema instal index zipkin2 schema index cql for keyspace zipkin2 2021 12 19 20 16 48 649 info 1 ing task 1 177 z s c schema upgrade schema zipkin2 schema upgrade 1 cql 2021 12 19 20 16 49 819 info 1 ing task 1 177 z s c schema upgrade schema zipkin2 schema upgrade 2 cql 2021 12 19 20 16 52 123 warn 1 orker epoll 2 1 z s i bodyisexceptionmessage unexpected error handling request but fail for some reason restart zipkin doesn t result in it try to recreate the schema again so it just remain in a failure state and I m not sure how to fix it attempt to run any query result in the follow error com datastax oss driver api core servererror invalidqueryexception table span by service do not exist at com datastax oss driver api core servererror invalidqueryexception copy invalidqueryexception java 48 java driver core 4 11 3 jar at com datastax oss driver internal core util concurrent completablefuture getuninterruptibly completablefuture java 149 java driver core 4 11 3 jar at com datastax oss driver internal core cql cqlpreparesyncprocessor process cqlpreparesyncprocessor java 59 java driver core 4 11 3 jar at com datastax oss driver internal core cql cqlpreparesyncprocessor process cqlpreparesyncprocessor java 31 java driver core 4 11 3 jar at com datastax oss driver internal core session defaultsession execute defaultsession java 230 java driver core 4 11 3 jar at com datastax oss driver api core cql synccqlsession prepare synccqlsession java 224 java driver core 4 11 3 jar at zipkin2 storage cassandra selectservicename factory selectservicename java 34 zipkin storage cassandra 2 23 15 jar at zipkin2 storage cassandra cassandraspanstore cassandraspanstore java 86 zipkin storage cassandra 2 23 15 jar at zipkin2 storage cassandra cassandrastorage spanstore cassandrastorage java 164 zipkin storage cassandra 2 23 15 jar at zipkin2 storage cassandra cassandrastorage serviceandspanname cassandrastorage java 176 zipkin storage cassandra 2 23 15 jar at zipkin2 server internal zipkinqueryapiv2 getremoteservicename zipkinqueryapiv2 java 117 class at com linecorp armeria internal server annotation annotatedservice invoke annotatedservice java 391 armeria 1 13 4 jar at com linecorp armeria internal server annotation annotatedservice lambda serve0 8 annotatedservice java 359 armeria 1 13 4 jar at java util concurrent completablefuture uniapply tryfire unknown source at java util concurrent completablefuture completion run unknown source at com linecorp armeria common requestcontext lambda makecontextaware 3 requestcontext java 547 armeria 1 13 4 jar at java util concurrent executors runnableadapter call unknown source at java util concurrent futuretask run unknown source at java util concurrent scheduledthreadpoolexecutor scheduledfuturetask run unknown source at java util concurrent threadpoolexecutor runworker unknown source at java util concurrent threadpoolexecutor worker run unknown source at io netty util concurrent fastthreadlocalrunnable run fastthreadlocalrunnable java 30 netty common 4 1 70 final jar 4 1 70 final at java lang thread run unknown source step to reproduce step to reproduce the behavior start dockerize zipkin and point it to an exist cassandra instance here be my environment var storage type cassandra3 cassandra ensure schema true cassandra contact point cassandra cassandra username cassandra cassandra password password expect behaviour 1 zipkin should be resilient and try to fix continue a fail migration 2 zipkin could output more helpful error message when fail a migration 3 fail migration should crash zipkin so operator know there be a problem 4 migration shouldn t fail |
openzipkinzipkin | big typo on version number on the github release page relate to log4j issue | Bug | the late release tag be 2 23 14 but the release info page have title say 2 23 4 I almost pull the incorrect docker image that still have log4j vulnerability by look at the title |
openzipkinzipkin | align appversion from chart with release version | Bug | describe the bug currently appversion be no align with the release version see l17 we should update that after l40 and then publish helm chart after l71 this will trigger a consistent workflow notice we wouldn t restrict helm chart publish to change in the chart itself by this change which actually make sense to I ping jonkerj |
openzipkinzipkin | mitigation for cve 2021 44228 | Bug | be there mitigation for the log4j vulnerability it appear that the dependency of spring boot starter log4j2 be use org apache log log4j log4j api 2 13 3 |
openzipkinzipkin | chart zipkin server elasticsearch support | Enhancement | rightnow chart zipkin server support only mem storage type as docker image allow to use elasticsearch I ve prepare deployment yaml file that support elasticsearch it be test and it work it doesn t require to make any change in value yaml as default storage type be still set to mem don t be hesitate to modify code it can always be well feature zipkin server helm chart that support elasticsearch jonkerj would you be so kind and verify it and add to code deployment file in attachment deployment zip |
openzipkinzipkin | multiple critical high severity vulnerability with apache tomcat tomcat embed core | Bug | describe the bug multiple high severity vulnerability with apache tomcat tomcat embed core we use prisma cloud in our environment to scan our build it have detect the follow issue with the zipkin image below I be wonder if these bug be exploitable in the context of zipkin and if they be be it possible at all to upgrade tomcat tomcat embed core to a new late version cve severity cvss package version status publish discover grace day description cve 2020 1938 critical 9 80 apache tomcat tomcat embed core 8 5 46 fix in 9 0 31 8 5 51 7 0 100 1 year 1 hour 627 when use the apache jserv protocol ajp care 1 year ago must be take when trust incoming connection to apache tomcat tomcat treat ajp connection as h cve 2021 41079 high 7 50 apache tomcat tomcat embed core 8 5 46 fix in 9 0 44 8 5 64 70 day 1 hour 57 apache tomcat 8 5 0 to 8 5 63 9 0 0 m1 to 9 0 43 70 day ago and 10 0 0 m1 to 10 0 2 do not properly validate incoming tls packet when tomcat be configure t cve 2021 25122 high 7 50 apache tomcat tomcat embed core 8 5 46 fix in 10 0 2 9 0 43 8 5 63 8 month 1 hour when respond to new h2c connection request 8 month ago apache tomcat version 10 0 0 m1 to 10 0 0 9 0 0 m1 to 9 0 41 and 8 5 0 to 8 5 61 could duplicate req cve 2020 17527 high 7 50 apache tomcat tomcat embed core 8 5 46 fix in 9 0 40 8 5 60 11 month 1 hour while investigate bug 64830 it be discover 11 month ago that apache tomcat 10 0 0 m1 to 10 0 0 m9 9 0 0 m1 to 9 0 39 and 8 5 0 to 8 5 59 could re use an http cve 2020 13935 high 7 50 apache tomcat tomcat embed core 8 5 46 fix in 9 0 37 8 5 57 7 0 105 1 year 1 hour 486 the payload length in a websocket frame be not 1 year ago correctly validate in apache tomcat 10 0 0 m1 to 10 0 0 m6 9 0 0 m1 to 9 0 36 8 5 0 to 8 5 56 and 7 cve 2020 13934 high 7 50 apache tomcat tomcat embed core 8 5 46 fix in 9 0 37 8 5 57 1 year 1 hour 486 an h2c direct connection to apache tomcat 1 year ago 10 0 0 m1 to 10 0 0 m6 9 0 0 m5 to 9 0 36 and 8 5 1 to 8 5 56 do not release the http 1 1 processor after cve 2020 11996 high 7 50 apache tomcat tomcat embed core 8 5 46 fix in 9 0 36 8 5 56 1 year 1 hour 504 a specially craft sequence of http 2 request 1 year ago send to apache tomcat 10 0 0 m1 to 10 0 0 m5 9 0 0 m1 to 9 0 35 and 8 5 0 to 8 5 55 could trigger hig cve 2019 17563 high 7 50 apache tomcat tomcat embed core 8 5 46 fix in 9 0 30 8 5 50 7 0 99 1 year 1 hour 690 when use form authentication with apache tomcat 1 year ago 9 0 0 m1 to 9 0 29 8 5 0 to 8 5 49 and 7 0 0 to 7 0 98 there be a narrow window where an attacker cve 2021 25329 high 7 00 apache tomcat tomcat embed core 8 5 46 fix in 10 0 2 9 0 43 8 5 63 8 month 1 hour the fix for cve 2020 9484 be incomplete when 8 month ago use apache tomcat 10 0 0 m1 to 10 0 0 9 0 0 m1 to 9 0 41 8 5 0 to 8 5 61 or 7 0 0 to 7 0 107 with cve 2020 9484 high 7 00 apache tomcat tomcat embed core 8 5 46 fix in 9 0 43 8 5 63 7 0 108 1 year 1 hour when use apache tomcat version 10 0 0 m1 to 1 year ago 10 0 0 m4 9 0 0 m1 to 9 0 34 8 5 0 to 8 5 54 and 7 0 0 to 7 0 103 if a cve 2019 12418 high 7 00 apache tomcat tomcat embed core 8 5 46 fix in 9 0 29 8 5 49 7 0 99 1 year 1 hour 690 when apache tomcat 9 0 0 m1 to 9 0 28 8 5 0 to 1 year ago 8 5 47 7 0 0 and 7 0 97 be configure with the jmx remote lifecycle listener a local attacker withou step to reproduce n a expect behaviour no vulnerability detect |
openzipkinzipkin | security scan on openzipkin zipkin 2 23 2 zipkin server zipkin server 2 23 2 exec jar identify a vulnerability cve 2021 22118 need a patch of zipkin server have 5 3 7 version of spring framework which will fix the vulnerability | Bug | cve 2021 22118 description in spring framework version 5 2 x prior to 5 2 15 and version 5 3 x prior to 5 3 7 a webflux application be vulnerable to a privilege escalation by re create the temporary storage directory a locally authenticate malicious user can read or modify file that have be upload to the webflux application or overwrite arbitrary file with multipart request datum currently the late zipkin server 2 23 5v be use 5 3 2 version spring framework which be vulnerable step to reproduce run a security scan use security scan tool expect behaviour need a patch of zipkin server have 5 3 7 version of spring framework which will fix the vulnerability I e update zipkin server to remove the vulnerability |
openzipkinzipkin | vulnerability cve 2021 38153 present in zipkin server 2 23 2 exec jar | Bug | security scan on openzipkin zipkin 2 23 2 zipkin server zipkin server 2 23 2 exec jar identify a vulnerability cve 2021 38153 need a patch of zipkin server have fix for this vulnerability cve 2021 38153 description some component in apache kafka use array equal to validate a password or key which be vulnerable to timing attack that make brute force attack for such credential more likely to be successful user should upgrade to 2 8 1 or high or 3 0 0 or high where this vulnerability have be fix the affect version include apache kafka 2 0 0 2 0 1 2 1 0 2 1 1 2 2 0 2 2 1 2 2 2 2 3 0 2 3 1 2 4 0 2 4 1 2 5 0 2 5 1 2 6 0 2 6 1 2 6 2 2 7 0 2 7 1 and 2 8 0 step to reproduce run a security scan use security scan tool expect behaviour need a patch of zipkin server have fix for this vulnerability I e update zipkin server to remove the vulnerability |
openzipkinzipkin | vulnerability cve 2021 26117 present in zipkin server 2 23 2 exec jar | Bug | security scan on openzipkin zipkin 2 23 2 zipkin server zipkin server 2 23 2 exec jar identify a vulnerability cve 2021 26117 need a patch of zipkin server have fix for this vulnerability cve 2021 26117 description the optional activemq ldap login module can be configure to use anonymous access to the ldap server in this case for apache activemq artemis prior to version 2 16 0 and apache activemq prior to version 5 16 1 and 5 15 14 the anonymous context be use to verify a valid user password in error result in no check on the password step to reproduce run a security scan use security scan tool expect behaviour need a patch of zipkin server have fix for this vulnerability I e update zipkin server to remove the vulnerability |
openzipkinzipkin | add github release to release tag | Enhancement | we have have a couple of new release tag but not accompany by github release we should add these include the change that go in |
openzipkinzipkin | docker image contain vulnerability cve 2020 13949 | Bug | describe the bug security scan of openzipkin zipkin 2 23 docker image have identify cve 2020 13949 in apache thrift 0 9 3 to 0 13 0 malicious rpc client could send short message which would result in a large memory allocation potentially lead to denial of service step to reproduce run a security scan use any docker image security scan tool expect behaviour update apache thrift to late version to remove the vulnerability |
openzipkinzipkin | docker image contain vulnerability cve 2021 37137 | Bug | describe the bug security scan of openzipkin zipkin 2 23 docker image have identify cve 2021 37137 the snappy frame decoder function doesn t restrict the chunk length which may lead to excessive memory usage beside this it also may buffer reserve skippable chunk until the whole chunk be receive which may lead to excessive memory usage as well this vulnerability can be trigger by supply malicious input that decompress to a very big size via a network stream or a file or by send a huge skippable chunk step to reproduce run a security scan use any docker image security scan tool expect behaviour update snappy decoder to late version to remove the vulnerability |
openzipkinzipkin | docker image contain vulnerability cve 2021 37136 | Bug | describe the bug security scan of openzipkin zipkin 2 23 docker image have identify cve 2021 37136 the bzip2 decompression decoder function doesn t allow set size restriction on the decompress output datum which affect the allocation size use during decompression all user of bzip2decoder be affect the malicious input can trigger an oome and so a dos attack step to reproduce run a security scan use any docker image security scan tool expect behaviour update bzip2 decompression decoder to late version to remove the vulnerability |
openzipkinzipkin | docker compose elasticsearch crash upon startup max virtual memory too low | Bug | describe the bug when attempt to use run docker compose f docker compose elasticsearch yml up result in an immediate docker crash on my machine error 1 bootstrap check fail 1 max virtual memory area vm max map count 65530 be too low increase to at least 262144 error elasticsearch do not exit normally check the log at elasticsearch log docker cluster log 2021 10 05t00 14 24 332 info o e n node zipkin elasticsearch stop uncaught exception in thread thread 2 java security accesscontrolexception access deny java lang runtimepermission getclassloader at java base java security accesscontrolcontext checkpermission unknown source at java base java security accesscontroller checkpermission unknown source at java base java lang securitymanager checkpermission unknown source at java base java lang classloader checkclassloaderpermission unknown source at java base java lang classloader getparent unknown source at org apache log log4j core selector classloadercontextselector locatecontext classloadercontextselector java 114 at org apache log log4j core selector classloadercontextselector getcontext classloadercontextselector java 74 at org apache log log4j core impl log4jcontextfactory getcontext log4jcontextfactory java 228 at org apache log log4j core impl log4jcontextfactory getcontext log4jcontextfactory java 45 at org apache log log4j logmanager getcontext logmanager java 174 at org elasticsearch bootstrap bootstrap 4 run bootstrap java 193 step to reproduce attempt to run docker compose with elasticsearch use the late zipkin tag expect behaviour a successful startup of zipkin and elasticsearch note I m run on window 10 pro 19041 1237 with wsl2 and ubuntu 20 04 as my distribution |
openzipkinzipkin | helm chart for zipkin | Enhancement | feature a helm chart to deploy zipkin on kubernete maintain by the openzipkin community helm chart be a very common mean to install software on kubernete there be a couple of chart for zipkin float around but warn opion ahead none of they be official up to date of good quality most mature project around kubernete offer chart support by the project nowadays rationale this make it easy for kubernete user to install zipkin example scenario n a prior art zipkin result on artifacthub we equinix manage service nl be willing to submit our own currently close source chart if it s go to be include upstream |
openzipkinzipkin | provider org mariadb jdbc internal com send authentication sendgssapiauthpacket could not be instantiate | Bug | run zipkin from dockercompose to store the file in mysql but the operation report an error here be my docker comemage yml file version 2 service zipkin image openzipkin zipkin container name zipkin environment storage type mysql point the zipkin at the storage backend mysql db zipkin mysql user mysqlname mysql pass mysqlpassword mysql host ip mysql tcp port 3306 port 9411 9411 |
openzipkinzipkin | download json fail | Bug | describe the bug I upload a trace json below and when I download it it fail with no output in the console the download ui in chrome show fail no file image step to reproduce step to reproduce the behavior upload this json traceid efe9cb8857f68c8f parentid efe9cb8857f68c8f i d 8608dc6ce5cafe8e kind server name get api timestamp 1627975249601797 duration 23457 localendpoint servicename backend ipv4 127 0 0 1 port 9000 tag http method get http path api jaxrs resource class resource jaxrs resource method printdate share true traceid efe9cb8857f68c8f parentid efe9cb8857f68c8f i d 8608dc6ce5cafe8f kind client name get timestamp 1627975249491667 duration 148265 localendpoint servicename frontend ipv4 127 0 0 1 port 8081 tag http method get http path api traceid efe9cb8857f68c8f i d efe9cb8857f68c8 g kind server name get timestamp 1627975249258448 duration 413469 localendpoint servicename frontend ipv4 127 0 0 1 port 8081 tag http method get http path jaxrs resource class resource jaxrs resource method callbackend download json in zipkin ui expect behaviour ideally the download succeed if not an error message be display explain why the download fail |
openzipkinzipkin | timestamprange calculation error due to int variable instead of long | Bug | timestamprange calculation error due to int variable instead of long cassandraspanstore java change need from final int indexttl to final long indexttl it will calculate wrong if ttl from table be set for 7890000 the result will be a bucket from the future |
openzipkinzipkin | annotation marker be mispace on the ui | Bug | when I annotate span the dot that show they on the timeline see the screenshot do not seem to be where it should as you can see the dot be in the very beginning while it s relative time be 4s and if you check the duration it should around the middle section of the bar this be my trace as you can see it start at 1625248613237960 and the annotation happen at 1625248616245438 1625248616245438 1625248613237960 1000 1000 3s json traceid 1c4ac61d32fce8f0 parentid 1c4ac61d32fce8f0 i d 39345d9b9b671972 name repair timestamp 1625248613237960 duration 10031051 localendpoint servicename example service ipv4 192 168 0 112 annotation timestamp 1625248616245438 value new tool tag author joshua bloch isbn 978 0134685991 title effective java traceid 1c4ac61d32fce8f0 i d 1c4ac61d32fce8f0 name buy timestamp 1625248612208230 duration 11082344 localendpoint servicename example service ipv4 192 168 0 112 tag author joshua bloch isbn 978 0134685991 title effective java I m run zipkin in docker this way docker compose yml I m use the late image from dockerhub org opencontainer image create 2020 12 25 org opencontainer image revision 7bf3aab83 |
openzipkinzipkin | link error in io zipkin zipkin2 zipkin package | Bug | describe the bug when linkage checker be run with io zipkin zipkin2 zipkin package add as a maven dependency it report the follow error class zipkin2 internal gson internal bind jsontreereader be not find reference by 1 class file zipkin2 internal gson stream jsonreader this be because of miss com google gson internal bind jsontreereader class when shade gson library in the pom file l83 package shade false true com google code gson gson com google gson stream jsonreader class com google gson stream jsontoken class com google gson stream malformedjsonexception class com google gson internal jsonreaderinternalaccess class com google gson zipkin2 internal gson module name apart from fix this would this cause any runtime error zipkin be a transitive dependency that be recently add to our system and not sure if the library that depend on it would break since this issue have be in several zipkin version it doesn t appear to be cause any issue but it would be great if you could confirm step to reproduce create a maven project add io zipkin zipkin2 zipkin as a dependency and include the linkage checker plugin then run mvn install to trigger the checker org apache maven plugin maven enforcer plugin 3 0 0 m3 com google cloud tool linkage checker enforcer rule 1 5 7 enforce maven enforce 3 3 9 enforce linkage checker verify enforce true |
openzipkinzipkin | can not send trace to elasticsearch 7 9 | Bug | describe the bug the version 2 23 1 can not send datum to elasticsearch version 7 9 the log be dec 23 08 35 47 localhost java 65500 2020 12 23 08 35 47 945 warn 65500 ing task 1 207 z s i bodyisexceptionmessage unexpected error handle req dec 23 08 35 47 localhost java 65500 java lang nullpointerexception null dec 23 08 35 47 localhost java 65500 at zipkin2 server internal elasticsearch initialendpointsupplier get initialendpointsuppli java 61 class dec 23 08 35 47 localhost java 65500 at zipkin2 server internal elasticsearch initialendpointsupplier get initialendpointsuppli java 28 class dec 23 08 35 47 localhost java 65500 at zipkin2 server internal elasticsearch lazyhttpclientimpl getendpoint lazyhttpclientimpl java 60 class dec 23 08 35 47 localhost java 65500 at zipkin2 server internal elasticsearch lazyhttpclientimpl get lazyhttpclientimpl java 52 class dec 23 08 35 47 localhost java 65500 at zipkin2 elasticsearch elasticsearchstorage http elasticsearchstorage java 387 zipkin storage elasticsearch 2 23 1 jar dec 23 08 35 47 localhost java 65500 at zipkin2 elasticsearch autovalue elasticsearchstorage http autovalue elasticsearchstorage java 43 zipkin storage elasticsearch 2 dec 23 08 35 47 localhost java 65500 at zipkin2 elasticsearch elasticsearchstorage doensureindextemplate elasticsearchstorage java 334 zipkin storage elasticsearch 2 2 dec 23 08 35 47 localhost java 65500 at zipkin2 elasticsearch elasticsearchstorage ensureindextemplate elasticsearchstorage java 327 zipkin storage elasticsearch 2 23 dec 23 08 35 47 localhost java 65500 at zipkin2 elasticsearch elasticsearchstorage spanstore elasticsearchstorage java 228 zipkin storage elasticsearch 2 23 1 jar dec 23 08 35 47 localhost java 65500 at zipkin2 server internal zipkinqueryapiv2 gettrace zipkinqueryapiv2 java 147 class dec 23 08 35 47 localhost java 65500 at sun reflect nativemethodaccessorimpl invoke0 native method 1 8 0 262 dec 23 08 35 47 localhost java 65500 at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java 62 1 8 0 262 dec 23 08 35 47 localhost java 65500 at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java 43 1 8 0 262 dec 23 08 35 47 localhost java 65500 at java lang reflect method invoke method java 498 1 8 0 262 dec 23 08 35 47 localhost java 65500 at com linecorp armeria internal server annotation annotatedservice invoke annotatedservice java 331 armeria 1 3 0 jar dec 23 08 35 47 localhost java 65500 at com linecorp armeria internal server annotation annotatedservice lambda serve0 6 annotatedservice java 306 armeria 1 3 0 jar dec 23 08 35 47 localhost java 65500 at java util concurrent completablefuture uniapply completablefuture java 616 1 8 0 262 dec 23 08 35 47 localhost java 65500 at java util concurrent completablefuture uniapply tryfire completablefuture java 591 1 8 0 262 dec 23 08 35 47 localhost java 65500 at java util concurrent completablefuture completion run completablefuture java 456 1 8 0 262 dec 23 08 35 47 localhost java 65500 at com linecorp armeria common requestcontext lambda makecontextaware 3 requestcontext java 502 armeria 1 3 0 jar dec 23 08 35 47 localhost java 65500 at io micrometer core instrument internal timedrunnable run timedrunnable java 44 micrometer core 1 6 1 jar 1 6 1 dec 23 08 35 47 localhost java 65500 at java util concurrent executors runnableadapter call executor java 511 1 8 0 262 dec 23 08 35 47 localhost java 65500 at java util concurrent futuretask run futuretask java 266 1 8 0 262 dec 23 08 35 47 localhost java 65500 at java util concurrent scheduledthreadpoolexecutor scheduledfuturetask access 201 scheduledthreadpoolexecutor java 180 1 8 0 262 dec 23 08 35 47 localhost java 65500 at java util concurrent scheduledthreadpoolexecutor scheduledfuturetask run scheduledthreadpoolexecutor java 293 1 8 0 262 dec 23 08 35 47 localhost java 65500 at java util concurrent threadpoolexecutor runworker threadpoolexecutor java 1149 1 8 0 262 dec 23 08 35 47 localhost java 65500 at java util concurrent threadpoolexecutor worker run threadpoolexecutor java 624 1 8 0 262 dec 23 08 35 47 localhost java 65500 at io netty util concurrent fastthreadlocalrunnable run fastthreadlocalrunnable java 30 netty common 4 1 54 final jar 4 1 54 final dec 23 08 35 47 localhost java 65500 at java lang thread run thread java 748 1 8 0 262 step to reproduce step to reproduce the behavior use elasticsearch 7 9 and zipkin 2 23 1 expect behaviour can use elasticsearch 7 9 as backend |
openzipkinzipkin | split github action test phase by docker | Enhancement | most of our project except maybe a couple collector honor the ddocker skip true flag it would be cool to split out the build so that the docker relate heavy test run concurrently ex switch normal case to build bin test ddocker skip true then add a matrix for the heavy thing that use testcontainer ex build bin test pl zipkin collector rabbitmq rabbitmq might be one miss the skip thing though p |
openzipkinzipkin | add docker build for s390x | Enhancement | feature to make the docker image for s390x z system available rational we be interested in knative on the z architecture s390x one of the core knative component evente use zipkin for the cloud event trace see the use case accessing trace in evente knative already have the multi arch nightly build include the s390x support so it make sense for we to use the same evente s390x stack as it have do for amd64 example scenario client who have z hardware and want to use knative on top of it can use zipkin without any technical hurdle |
openzipkinzipkin | bad request when use maxduration or minduration search condition | Enhancement | the zipkin version be 2 22 1 other query condition be fine just duration return code 400 |
openzipkinzipkin | dependency didn t show anything when use elasticsearch storage | Enhancement | hi I m use zipkin 2 22 1 version and find the dependency always empty I can see datum in trace here be my running script java jar zipkin server 2 22 1 exec jar storage type elasticsearch eshost kafka bootstrap server and when I remove the storaget type and eshost use in memory mode I can see the dependency |
openzipkinzipkin | advice for action auto create index | Enhancement | varuna mention his site disabled action auto create index and think it would be helpful to document folk to check on this before use zipkin in a share cluster there s some question of where to document that and what to document for example this seem to be a normal non aw feature but not sure the version range it apply to index creation particularly there s recent activity on this topic any advice openzipkin elasticsearch |
openzipkinzipkin | junk in console startup output | Bug | zipkin 2020 11 11 06 32 55 666 main error incorrect number of option on style expect at least 1 receive 0 zipkin 2020 11 11 06 32 55 681 main warn class org springframework boot log log4j2 colorconverter do not extend patternconverter zipkin 2020 11 11 06 32 55 683 main error unrecognize conversion specifi clr start at position 4 in conversion pattern zipkin 2020 11 11 06 32 55 684 main error incorrect number of option on style expect at least 1 receive 0 zipkin 2020 11 11 06 32 55 685 main warn class org springframework boot log log4j2 colorconverter do not extend patternconverter zipkin 2020 11 11 06 32 55 685 main error unrecognize conversion specifi clr start at position 14 in conversion pattern zipkin zipkin oo zipkin oooo zipkin oooooo zipkin oooooooo zipkin oooooooooo zipkin oooooooooooo zipkin ooooooo ooooooo zipkin oooooo ooooooo zipkin oooooo ooooooo zipkin oooooo o o oooooo zipkin oooooo oo oo oooooo zipkin ooooooo oooo oooo ooooooo zipkin oooooo ooooo ooooo ooooooo zipkin oooooo oooooo oooooo ooooooo zipkin oooooooo oo oo oooooooo zipkin ooooooooooooo oo oo ooooooooooooo zipkin oooooooooooo oooooooooooo zipkin oooooooo oooooooo zipkin oooo oooo zipkin zipkin zipkin zipkin zipkin zipkin zipkin zipkin version 2 22 2 commit 0b246dd zipkin |
openzipkinzipkin | itcassandra fail to run on arm64 | Bug | we should double check the base layer actually work on arm64 as it be a different layer than other image jre 1 8 exec format error be sometimes accidentally run the wrong arch cc odidev 2020 11 10 14 21 32 342 main error ghcr io openzipkin zipkin cassandra 2 22 1 log output from the fail container standard init linux go 211 exec user process cause exec format error 2020 11 10 14 21 32 342 main warn zipkin2 storage cassandra v1 cassandrastorageextension couldn t start docker image ghcr io openzipkin zipkin cassandra 2 22 1 container startup fail |
openzipkinzipkin | itkafkacollector not run in travis either arch | Bug | I think there s some drift possibly due to a change in log configuration this seem unrelated to amd64 vs arm64 cc odidev we should change this to a simple healthcheck condition info run zipkin2 collector kafka itkafkacollector 2020 11 10 14 33 23 106 main info zipkin2 collector kafka kafkacollectorrule start docker image ghcr io openzipkin zipkin kafka 2 22 1 2020 11 10 14 34 29 172 main error ghcr io openzipkin zipkin kafka 2 22 1 could not start container org testcontainer container containerlaunchexception time out wait for log output match info kafkaserver i d 0 start |
openzipkinzipkin | add scribecollector port | Enhancement | scribecollector port should be public allow read back of the actual listen port in netty server channel localaddress port this allow you to indicate builder port 0 to have it bind an anonymous port particularly this will help the zipkin reporter project which be suffer from test flake recently due to lifecycle |
openzipkinzipkin | find a replacement for rabbitmq 3 8 management alpine | Enhancement | rabbitmq 3 8 management alpine use by rabbitmqcollectorrule be a docker hub registry image which mean each time a pull request run potentially this decrement a count and possibly can cause a build outage can someone help find a replacement registry for it ex in ghcr io gcr io or quay possibly we can layer it on our own image not sure how complex it be cc shakuzen make bsideup |
openzipkinzipkin | replace zipkin builder docker image with direct maven instead | Enhancement | we currently use openzipkin zipkin builder instead of normal jdk so that docker bin install sh can build maven from within docker to produce a snapshot build we no long use this branch instead use a flag release from context which re use file from the docker context stage by the last mvn package invocation in do the arch work I find it extremely slow and difficult to test zipkin builder because to build it require download a lot of npm and maven artifact I think we should abandon this as to my knowledge it be only make for docker hub build and we no long build master with docker hub we do it in travis even if we do it in another ci it would be able to run java or our image in bad case so the idea be to remove the building from source section from docker bin install sh replace all usage of zipkin builder with the normal jdk image not jre classifier in docker build image if the tag be master and release from context be not set invoke maven like it say at the bottom of zipkin server readme md remove the job from travis yml which republish zipkin builder delete the zipkin builder package from the github org |
openzipkinzipkin | be rocketmq and postgresql support | Enhancement | would you like to know which of these two support or neither where can I check my datum |
openzipkinzipkin | flakey test deduplicatinginsertt exceptionsinvalidate enqueue | Bug | expect actual not to be empty at zipkin2 storage cassandra internal call deduplicatinginsertt exceptionsinvalidate enqueue deduplicatinginsertt java 90 at java base jdk internal reflect nativemethodaccessorimpl invoke0 native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java 62 at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java 43 at java base java lang reflect method invoke method java 566 at org junit runner model frameworkmethod 1 runreflectivecall frameworkmethod java 59 at org junit internal runner model reflectivecallable run reflectivecallable java 12 |
openzipkinzipkin | zipkin trace mq asyn | Enhancement | I m very interested in zipkin but our project use rabbitmq syn and asyn how to trace mq and asyn call use zipkin thank you very much |
openzipkinzipkin | zipkin elasticsearch module didn t create timestamp millis field for version 2 21 7 | Bug | I be use zipkin elasticsearch library to create a new zipkin server for our company usage and I be use version 2 21 7 version and in 2016 for ticket 1209 we already define a method call prefixwithtimestampmillis in elasticsearchspanconsumer java for create a date field timestamp mill and this be very convenient for create event base kibana dashboard but for this version 2 21 7 this method be go and the timestamp for each span again turn to epoch millis do you why we remove this method |
openzipkinzipkin | zipkin ui always show empty result | Bug | describe the bug I setup zipkin with cassandra3 as storage type it seem that the zipkin ui always display empty result however it seem that the total result be more than zero as highlight in yellow color in the screenshot below image expect behaviour zipkin ui should display list of trace result |
openzipkinzipkin | total duration in overview wrongly say ms | Bug | in the overview the total duration for a trace be show as 15 714ms but the total trace duration be 15 714s image image |
openzipkinzipkin | inline replace git commit i d abbrev in ci instead of rely on git | Enhancement | the git folder on a default clone copy 77 mb into the docker context we only need it for the git commit i d plugin which replace git commit i d abbrev in a couple file in the zipkin server directory if you don t have the git folder the replacement fail silently and the server console look like this version 2 21 8 snapshot commit git commit i d abbrev instead of this version 2 21 8 snapshot commit ef5f838 we definitely want the git sha but in ci we should be able to get it another way if we have it we could replace git commit i d abbrev use se instead and no long need the massive git directory in our docker context when this issue be finish git will no long be in the dockerignore file |
openzipkinzipkin | migrate our docker image consistently to alpine | Bug | openzipkin zipkin builder image be run a different distro which be ok but it be a lot large to download than necessary one thing block this be as we can t execute the build when node isn t work require to be what s download from the plugin |
openzipkinzipkin | empty trace list despite match | Bug | describe the bug the ui see screenshot do not display any span even though there be some search result in fact the follow json be return by the zipkin backend when I inspect the network request json traceid 9e8189bd08e4493c i d 9e8189bd08e4493c name rxjava timestamp 1600443526950815 duration 111 localendpoint servicename gateway ipv4 10 8 2 4 tag thread rxioscheduler 2 traceid af4b1f57aff1be73 i d af4b1f57aff1be73 name rxjava timestamp 1600443525451017 duration 106 localendpoint servicename gateway ipv4 10 8 2 4 tag thread rxioscheduler 2 traceid dfe4e47cf3ce99b2 i d dfe4e47cf3ce99b2 name rxjava timestamp 1600443525951231 duration 84 localendpoint servicename gateway ipv4 10 8 2 4 tag thread rxioscheduler 2 traceid 0490f0c3a01ff5dd i d 0490f0c3a01ff5dd name rxjava timestamp 1600443524450494 duration 94 localendpoint servicename gateway ipv4 10 8 2 4 tag thread rxioscheduler 2 traceid 0734dc2ed65857fd i d 0734dc2ed65857fd name rxjava timestamp 1600443527951278 duration 158 localendpoint servicename gateway ipv4 10 8 2 4 tag thread rxioscheduler 2 traceid 1013644077ac0343 i d 1013644077ac0343 name rxjava timestamp 1600443526450430 duration 109 localendpoint servicename gateway ipv4 10 8 2 4 tag thread rxioscheduler 2 traceid 1e5a32410a5163fe i d 1e5a32410a5163fe name rxjava timestamp 1600443524950742 duration 99 localendpoint servicename gateway ipv4 10 8 2 4 tag thread rxioscheduler 2 traceid 26ecb5641540a59c i d 26ecb5641540a59c kind server name get timestamp 1600443526083376 duration 2207 localendpoint servicename gateway ipv4 10 8 2 4 remoteendpoint ipv4 35 199 77 186 tag http method get http path mvc controller class resourcehttprequesthandler traceid 376e9201cc15f3e3 i d 376e9201cc15f3e3 name rxjava timestamp 1600443523951278 duration 120 localendpoint servicename gateway ipv4 10 8 2 4 tag thread rxioscheduler 2 traceid 5f2c0aa9171388cb i d 5f2c0aa9171388cb name rxjava timestamp 1600443527451075 duration 95 localendpoint servicename gateway ipv4 10 8 2 4 tag thread rxioscheduler 2 step to reproduce step to reproduce the behavior deploy openzipkin docker image late as of september 18th 2020 in kubernete with a mysql storage open the zipkin ui click the search icon here a limit of 10 be set and no filter but any combination yield the same result expect behaviour the expect behaviour be that the trace be display correctly |
openzipkinzipkin | flakey test itelasticsearchhealthcheck onehealthy | Bug | error zipkin2 server internal elasticsearch itelasticsearchhealthcheck onehealthy time elapse 0 078 s failure org opentest4j assertionfailederror expect to be equal to but be not at zipkin2 server internal elasticsearch itelasticsearchhealthcheck onehealthy itelasticsearchhealthcheck java 106 |
openzipkinzipkin | show new line in ui | Enhancement | feature add white space pre line or equivalent style to show new line in tag information rational in previous version new line be show this allow user to read easily the multiline tag information example scenario read multiline tag information prior art image image |
openzipkinzipkin | prevent criterion from flicker | Bug | if you look carefully sometimes criterion flicker this pr fix it simply put I adjust the timing of the rendering so that no extra drawing occur |
openzipkinzipkin | improve search result table s design | Enhancement | the current search result table be cluttered and the code be more complicated than it need to be so I ve update these component from scratch before after featrue collapssible feature collapsible filtering by service name feature filter sortable feature sortable |
openzipkinzipkin | add changelog | Enhancement | there be no obvious way to see all the change from different version of zipkin there should be a changelog file with the usual information about bugfixe new feature and break change whenever a release happen there should also be a short mention of the changelog in the readme |
openzipkinzipkin | requirement zipkin setup on linux machine | Enhancement | please share the document or guide for instrument zipkin on linux machine I have start new project for zipkin |
openzipkinzipkin | use redux toolkit to reduce boilerplate code | Enhancement | relate 3144 redux toolkit reduce a lot of boilerplate code need for redux |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.