Are you trying to troubleshoot inability to connect to elasticsearch? If so, you can set ES_HTTP_LOGGING=BASIC for example
also /prometheus will have a lot of stats about the client
but I don't understand the relationship between TLS/https and the stack trace you mention because the port is the plain text one (9200)
there are deeper logging options available, but I would first check the node your server is on can reach 10.0.88.33:9200 using http protocol
@adriancole I used zipkin-js-example as input to debug my implementation of zipkin-js and tha's how I was able to generate the logs.. In my case I have a Node service that uses express (called service in the earlier log) instrumented pretty much as zipkin-js-example, however the service makes calls to other backend services (target-a and target-b in the previous log) using zipkin-instrumentation-request-promise.
Helicopter view of the service flow is: call -> express -> route controller (singleton) -> invoker (singleton). Isinvoker that implements zipkin-instrumentation-request-promise pretty much as described in Using the Request class section of https://github.com/openzipkin/zipkin-js/tree/master/packages/zipkin-instrumentation-request-section.
The issue described appears when a given call takes longer to be processed (by the controller) than a newer call. In the logs I shared the two calls are represented with two distinct traceIds:1000000000000001 and 1000000000000002.
you just call it twice in the same pattern
because I think this hasn't to do with the endpoints being on different hosts
rather something about how the propagation is going
then you might be able to get a branch off normal example with only several lines changed in other words
easier to solve
@stanltam_twitter looking at image now..
so you are literally listening on ssl to the same port as not ssl?
Actually I have already set to https... and the elastic is using 9200 for https port. I am able to use logstash to connect with port 9200...
Seems prometheus API don't return much hints...
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.0",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.5",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.75",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.9",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.95",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.98",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.99",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.999",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="1.0",} 256.0
elasticsearch_healthcheck_responseLength_count{httpStatus="400",method="GET",} 4.0
elasticsearch_healthcheck_responseLength_sum{httpStatus="400",method="GET",} 1036.0
elasticsearch_healthcheck_responseLength_max{httpStatus="400",method="GET",} 259.0
elasticsearch_healthcheck_timeouts_total{cause="ResponseTimeoutException",httpStatus="400",method="GET",} 0.0
elasticsearch_healthcheck_timeouts_total{cause="WriteTimeoutException",httpStatus="400",method="GET",} 0.0
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.0",} 0.006291456
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.5",} 0.007077888
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.75",} 0.007077888
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.9",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.95",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.98",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.99",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.999",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="1.0",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds_count{httpStatus="400",method="GET",} 4.0
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds_sum{httpStatus="400",method="GET",} 0.356786771
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds_max{httpStatus="400",method="GET",} 0.336022085
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.0",} 0.001376256
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.5",} 0.001769472
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.75",} 0.001769472
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.9",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.95",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.98",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.99",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.999",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="1.0",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds_count{httpStatus="400",method="GET",} 4.0
elasticsearch_healthcheck_totalDuration_seconds_sum{httpStatus="400",method="GET",}
Seems prometheus API don't return much hints...
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.0",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.5",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.75",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.9",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.95",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.98",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.99",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="0.999",} 256.0
elasticsearch_healthcheck_responseLength{httpStatus="400",method="GET",quantile="1.0",} 256.0
elasticsearch_healthcheck_responseLength_count{httpStatus="400",method="GET",} 4.0
elasticsearch_healthcheck_responseLength_sum{httpStatus="400",method="GET",} 1036.0
elasticsearch_healthcheck_responseLength_max{httpStatus="400",method="GET",} 259.0
elasticsearch_healthcheck_timeouts_total{cause="ResponseTimeoutException",httpStatus="400",method="GET",} 0.0
elasticsearch_healthcheck_timeouts_total{cause="WriteTimeoutException",httpStatus="400",method="GET",} 0.0
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.0",} 0.006291456
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.5",} 0.007077888
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.75",} 0.007077888
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.9",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.95",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.98",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.99",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="0.999",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds{httpStatus="400",method="GET",quantile="1.0",} 0.352059392
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds_count{httpStatus="400",method="GET",} 4.0
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds_sum{httpStatus="400",method="GET",} 0.356786771
elasticsearch_healthcheck_connectionAcquisitionDuration_seconds_max{httpStatus="400",method="GET",} 0.336022085
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.0",} 0.001376256
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.5",} 0.001769472
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.75",} 0.001769472
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.9",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.95",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.98",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.99",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="0.999",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds{httpStatus="400",method="GET",quantile="1.0",} 0.010420224
elasticsearch_healthcheck_totalDuration_seconds_count{httpStatus="400",method="GET",} 4.0
elasticsearch_healthcheck_totalDuration_seconds_sum{httpStatus="400",method="GET",}
ok so you are asking how to change the TLS setup used by the client, not the server listener
I think before I misunderstood or maybe two people ask different tls questions at the same time :P
first let me check last TLS answer :
@mvbjoshi seems default spring boot properties for ssl should already work, can you just try it please? line/armeria#1663
@stanltam_twitter that answer isn't for you heh
lemme first get the server thing going.. changing tests
@mvbjoshi specifically you will want to set properties like this https://github.com/line/armeria/blob/master/spring/boot-autoconfigure/src/main/java/com/linecorp/armeria/spring/ArmeriaSettings.java#L35-L49
as this is spring boot you can choose whether you want to do that with --x.y.z=value or an additional properties file, or something else
@stanltam_twitter openzipkin/zipkin#2774
usually response time is less than a day, so happy friday :P
adriancole @adriancole wanders away but will check back in a couple answers in case magic happens
keystore, truststore and passwords
hoping it works. I'll check up in the morning
gnight
Can someone tell me if it's it possible to instrument a graph of processors like this? https://github.com/bbejeck/kafka-streams/blob/69e366e767f9a019a499514364ac86bfbdc93f4e/src/main/java/bbejeck/processor/purchases/PurchaseProcessorDriver.java#L55-L65
can't find any similar examples in the zipkin github repo
@bhaveshhpatel if you are using sleuth, it already does this sort of thing. can you rephrase what you need? maybe already covered? https://cloud.spring.io/spring-cloud-sleuth/reference/html/#_propagating_extra_fields
@owenloui I think you're looking for this https://github.com/openzipkin/brave/tree/master/instrumentation/kafka-streams