OpenTelemetry를 사용한 Linkerd 모니터링 문제 해결

$
kubectl get pods -n newrelic
$
kubectl logs -n newrelic deployment/my-opentelemetry-collector | grep -E "error|warn|Failed" | tail -20

$
# Verify Java agent loaded (for APM-instrumented app pods)
$
kubectl logs -n <YOUR_NAMESPACE> deployment/<YOUR_APP> | grep "javaagent"
$

$
# Verify Linkerd proxy routing for OTLP gRPC (must show appProtocol: grpc)
$
kubectl get svc -n newrelic my-opentelemetry-collector -o jsonpath='{.spec.ports}'

$
kubectl patch svc -n newrelic my-opentelemetry-collector --type='json' \
>
  -p='[{"op":"add","path":"/spec/ports/1/appProtocol","value":"grpc"}]'

$
kubectl exec -n <YOUR_NAMESPACE> deployment/<YOUR_APP> -- env | grep MY_POD_IP

$
# OTel Collector Contrib (separate DaemonSet release for logs)
$
kubectl exec -n newrelic daemonset/my-opentelemetry-collector-logs -- ls /var/log/pods 2>/dev/null | head -5
$

$
# NRDOT (built-in, same DaemonSet as metrics/traces)
$
kubectl exec -n newrelic daemonset/nr-k8s-otel-collector-daemonset -- ls /var/log/pods 2>/dev/null | head -5