Why is this path not excluded from the tracing

[jeroenjacobs79]

We have SpringBoot applications that have an actuator running on port 8081 on path /actuator/health. I want to exclude those from Jaeger tracing, so I tried the following config:

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: jaeger-production
  namespace: istio-system-upgrade
spec:
  allInOne:
    config: {}
    metricsStorage: {}
    options: {}
    resources: {}
  resources:
    limits:
      cpu: 250m
      memory: 200Mi
    requests:
      cpu: 20m
      memory: 128Mi
  agent:
    config: {}
    options: {}
    resources: {}
  sampling:
    options:
      default_strategy:
        operation_strategies:
          - operation: /actuator/health
            param: 0
            type: probabilistic
        param: 1
        type: probabilistic
  query:
    metricsStorage: {}
    options: {}
    resources: {}
  collector:
    config: {}
    kafkaSecretName: ''
    options:
      sampling:
        strategies-reload-interval: 30s
    resources: {}
  ingester:
    config: {}
    kafkaSecretName: ''
    options: {}
    resources: {}
  strategy: production
  storage:
    cassandraCreateSchema: {}
    dependencies:
      resources: {}
      schedule: 55 23 * * *
    elasticsearch:
      name: elasticsearch
      nodeCount: 3
      redundancyPolicy: SingleRedundancy
      resources:
        limits:
          memory: 10Gi
        requests:
          cpu: 250m
          memory: 8Gi
      storage:
        size: 200Gi
        storageClassName: ssd-3800g
    esIndexCleaner:
      enabled: true
      numberOfDays: 2
      resources: {}
      schedule: 55 23 * * *
    esRollover:
      resources: {}
      schedule: 0 0 * * *
    grpcPlugin: {}
    options: {}
    type: elasticsearch

Aas you can see, the sampling rate is set to 0 for /actuator/health, but still they show up in the tracing. What am I missing? Do I have to include the port number in the strategy in some way?

Also, are wildcards supported? I want to exclude everything from the actuator endpoint, so can I use /actuator/* in the strategy pattern?

Thanks.

[yurishkuro]

1. which SDK are you using? Does it support Jaeger's remote sampling?
2. are you sure operation_strategies is supposed to be nested under default_strategy?

[jeroenjacobs79]

1. Everything is sampled (including the actuator endpoints), so yeah, tracing is working. The default strategy certainly works.
2. In plain Jaeger, operation strategies can be part of the default strategy, as documented by jaeger itself: https://www.jaegertracing.io/docs/1.44/sampling/. I assume the operator follows the same pattern.

[yurishkuro]

Everything is sampled doesn't mean it is so because of remote config; the OTEL SDKs, for example, default to 100%. Were you able to observe different sampling rates when changing remote config?

[yurishkuro]

My Q2 is easy to verify by curl /sampling?service=yourservice

[jeroenjacobs79]

I'm sorry, I have no clue what point you are trying to make. I'm not a Java dev, I'm just one of the people maintaining the Kubernetes cluster. According to the information I am given, we don't use OpenTelemetry, but the old Java way of doing it (whatever that might mean). I have no reason to doubt that the default strategy is what's being used.

Not sure what you are trying to say with that curl command either. What should I query, jaeger itself you mean? Sorry, your explanation is unclear to me.

[yurishkuro]

I added some troubleshooting steps to the docs https://www.jaegertracing.io/docs/1.44/troubleshooting/#remote-sampling