Robert Ma
* Misk is head of master; jetty is v10.0.15 * Nothing in Java logs; I'll check agent logs * ` -Dtrace.Status404Rule.enabled=false -Ddd.sqs.propagation.enabled=false -Ddd.sqs.legacy.tracing.enabled=true` I'll try to reproduce again and file...
Here's the content of `-Ddatadog.slf4j.simpleLogger.logFile`: ``` [dd.trace 2023-09-07 21:39:26:461 +0000] [dd-task-scheduler] INFO datadog.trace.agent.core.StatusLogger - DATADOG TRACER CONFIGURATION {"version":"1.20.1~70cd67ce90","os_name":"Linux","os_version":"5.10.184-175.731.amzn2.x86_64","architecture":"amd64","lang":"jvm","lang_version":"17.0.8.1","jvm_vendor":"Eclipse Adoptium","jvm_version":"17.0.8.1+1","java_class_version":"61.0","http_nonProxyHosts":"null","http_proxyHost":"null","enabled":true,"service":"","agent_url":"","agent_unix_domain_socket":"/var/run/datadog/apm.socket","agent_error":false,"debug":false,"trace_propagation_style_extract":["datadog"],"trace_propagation_style_inject":["datadog"],"analytics_enabled":false,"sampling_rules":[{},{}],"priority_sampling_enabled":true,"logs_correlation_enabled":true,"profiling_enabled":true,"remote_config_enabled":true,"debugger_enabled":false,"appsec_enabled":"ENABLED_INACTIVE","telemetry_enabled":true,"dd_version":"240f05dfa15915f7b8b2882eb0443fbe60872b26","health_checks_enabled":true,"configuration_file":"no config file present","runtime_id":"","logging_settings":{"levelInBrackets":false,"dateTimeFormat":"'[dd.trace 'yyyy-MM-dd HH:mm:ss:SSS Z']'","logFile":"/var/log/datadog.log","configurationFile":"simplelogger.properties","showShortLogName":false,"showDateTime":true,"showLogName":true,"showThreadName":true,"defaultLogLevel":"INFO","warnLevelString":"WARN","embedException":false},"cws_enabled":false,"cws_tls_refresh":5000,"datadog_profiler_enabled":true,"datadog_profiler_safe":true,"datadog_profiler_enabled_overridden":false} ```
In other words, it is still present in 1.21.1. Filing a support ticket, too (1334466).
https://github.com/linkerd/linkerd2-proxy/blob/986d45895c0945152828e1286f7b5714520a86ba/linkerd/http-retry/src/replay.rs#L152
Some debug logging: ``` {"timestamp":"[ 1269.373381s]","level":"DEBUG","fields":{"message":"client connection open"},"target":"linkerd_transport_metrics::client","spans":[{"name":"inbound"},{"port":80,"name":"server"},{"name":"backend-web.default.svc.cluster.local:80","name":"http"},{"name":"profile"},{"name":"http1"}],"threadId":"ThreadId(1)"} {"timestamp":"[ 1269.375560s]","level":"DEBUG","fields":{"state":"Some(State { classify: Grpc(Codes({2, 4, 7, 13, 14, 15})), tx: Sender { chan: Tx { inner: Chan { tx: Tx {...
@hawkw do you know how to enable `RUST_BACKTRACE` in linkerd-proxy?
Hmm is it? I thought circuit breaker was a service-level concept and would be useful to stop sending traffic to the whole service (or route), but here we are talking...
Oh cool. However, it appears that circuit breaking doesn't work with service profiles. What about `HTTPRoute`? We need to specify retry behaviours.
It seems that async profiling is enabled by default since 1.3.0 and switched to https://github.com/DataDog/java-profiler since 1.5.0. Does that mean this is effectively "fixed"?
You can use my fork https://github.com/Hexcles/nginx-errors --- Sent from my cellphone. On Thu, Feb 9, 2023, 02:37 ucinskij ***@***.***> wrote: > Hi @strongjz , > I don't intend to put...