Please answer these questions before submitting your issue.

• Why do you submit this issue?
  I want to use skywaling with brpc-java.
  https://github.com/baidu/brpc-java

• Question or discussion
  discussion

• Bug
  no

• Requirement
  yes

• Feature or performance improvement
  Feature

Question

• What do you want to know?

Bug

• Which version of SkyW

https://github.com/openzipkin/zipkin/blob/master/zipkin/src/main/java/zipkin2/Span.java#L759

tags = builder.tags == null ? Collections.emptyMap() : new LinkedHashMap<>(builder.tags);

The empty map is immutable and makes it difficult to add a tag to a already created span. This will be helpful with performance. Otherwise, have to turn it in to builder and back to a Span when this type is us

Title: Openwhisk Plugin Contribution

Link: https://github.com/lopiter/pinpoint/tree/add-openwhisk-plugin
Target: Openwhisk
Supported Version: 0.0.1-SNAPSHOT
Description: serverless open source platform Openwhisk(https://openwhisk.apache.org)
before, akka-http plugin should be installed
ServiceTypes: OPENWHISK_INTERNAL , OPENWHISK_INVOKER
Configurations:

• profiler.openwhisk.enable : set

developer guide: development note for Middleware Engineering

• why need Middleware Engineering
• how to do it

Middleware Engineering 🔥, like multi-version Java full support(support low version Java and full functions of high version Java), is boring but essential for middleware! 🤣

https://github.com/alibaba/transmittable-thread-local/releases/tag/v2.5.0

There was a huge performance problem when using sleuth in the reactive stack. See here

This was partially addressed by this

But the downside 1478 of contents of MDC would be lost anytime event

What version of OpenCensus are you using?

HEAD of this repo

What version of Go are you using?

go version go1.13.4 darwin/amd64

Details

examples.PrintExporter seems to require being passed to view.RegisterExporter, but examples.LogExporter can't be passed there because it doesn't implement the write Exporter type. Instead, you're expected to run the Start metho

makes no sense. javadoc doesn't fail locally and these are all public types. Something's up https://circleci.com/gh/spring-cloud/spring-cloud-sleuth/6054

I will disable javadoc enforcement for now.

[WARNING] Javadoc Warnings
[WARNING] /root/project/spring-cloud-sleuth-core/src/main/java/org/springframework/cloud/sleuth/instrument/web/HttpClientRequestParser.java:44: warning - Tag @link

The textual information does match with the screenshot mentioned in the page:
https://kamon.io/docs/latest/guides/installation/setting-up-the-agent/#in-a-nutshell
The test refers to kanela jar whereas the screenshot refers to aspectjweaver

Currently websockets are unsupported:

class SttpBackendStub[F[_], S] private (
    monad: MonadError[F],
    matchers: PartialFunction[Request[_, _], F[Response[_]]],
    fallback: Option[SttpBackend[F, S, NothingT]]
) extends SttpBackend[F, S, NothingT] { // TODO

(note the TODO for the NothingT type parameter which specifies what kind of websockets are supported).

The bac

Requirement - what kind of business use case are you trying to solve?

Configuration that can affect service performance and would ideally live and be deployed with the service code & configuration.

For example, debugging an individual service issue might start with a focus on the service itself. At the moment, remote sampling strategies could be configured remotely. One might not think to

move apm-server.capture_personal_data to apm-server.rum.capture_personal_data. I propose:

• deprecate immediately (7.x)
• keep deprecated in 8.x
• remove in 9.0

If both are set, use apm-server.rum.capture_personal_data

I followed the steps:
$ kubectl apply -f kubernetes/client-side-lb-api/echo-server.yaml
$ kubectl apply -f kubernetes/client-side-lb-api/echo-client.yaml
$ kubectl get pods -l run=echo-client
with this step:
$ kubectl logs -f echo-client...
I found java error

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SL

We don't need to provide very detailed development document, but at least, we should have one about How to add a new widget for new metric. Do you agree? From my perspective, in current UI architecture, this would become one very interesting point for new contributor.

Hi,

I'm wondering if there are any samples or guidance that could be given on how to configure the OpenTracing shim? I'm having trouble working out how to configure it up inside an Asp.Net Core app.

Thanks.

Requirement - what kind of business use case are you trying to solve?

Always use time units in the Web UI which are easy to read by humans.

We use Jaeger to trace some complex, long-running offline jobs in which a seconds granularity in the Web UI is too fine-grained for human consumption.

Problem - what in Jaeger blocks you from solving the requirement?

Currently, durations seem

Currently, responses with status code <200 are being marked as errors.

https://github.com/openzipkin/zipkin-js/blob/master/packages/zipkin/src/instrumentation/httpServer.js#L91
https://github.com/openzipkin/zipkin-js/blob/master/packages/zipkin/src/instrumentation/httpClient.js#L43

Comes from openzipkin/brave#874

Ping @adriancole @ghermeto

Is your feature request related to a problem? Please describe.

I am unable to add instrumentation for Global Objects in the agent in a way that is described here. There are few methods that I needed to instrument like eval(), setTimeout() etc.
(PS: I don't know if I am approaching this right)

**Describe the solution you'd li

Cannot use same trace ID accross different node of microservices

On the document of https://opentracing.io/docs/overview/tracers/#propagating-a-trace-with-inject-extract, there is a concept of inject and extract. This is working fine with http carrier. Yet, I cannot reproduce this with Text Map carrier.

Please create a doc for u

Currently the default propagator is a noop propagator. According to the spec:

If offered, the global Propagators should default to a composite Propagator
containing W3C Trace Context and Correlation Context Propagators,
in order to provide propagation even in the presence of no-op
OpenTelemetry implementations.

Often it is useful to add remoteEndpoint to the client spans. Specifically http requests.

Currently nor the client or the transport support this functionality. The most logical options that comes to my mind is that we add an option for both.

Ping @basvanbeek @adriancole

Validate timeout response from SDK. Original suspicion was that ingestion service timeouts cause SDK to timeout and retry. We are lacking documentation on what happens on endpoint timeouts.
a. What’s the default timeout on SDK?
b. Do we retry on timeout?
c. Is it a good idea to increase the number of workers to a very big number to prevent timeout-caused delays?