Jaeger shows just hisself as api and none other service

Policies and Telemetry
1

Hi.

I’ve installed Istio not using Helm. Followed this tutorial: https://istio.io/docs/setup/kubernetes/install/kubernetes/ As far as I understood by the docs tracing is enabled by default. I’ve checked the populate trace value which is at 100%.

Any steps which I can perfom to solve this issue? My sidecars are correctly configured.
Would an installation using Helm solve this issue?

Any help is much appreciated.

Thanks a lot

2

I’m not sure I fully understand the issue that are you seeing. Would you mind providing more details about the observed issue?

I think troubleshooting the issue may be complicated by your custom install. I can recommend, however, starting with the FAQ on distributed tracing: https://istio.io/help/faq/distributed-tracing/

In particular, you may want to read: https://istio.io/help/faq/distributed-tracing/#no-tracing

3

I had a look at both of the links. My naming conventions should work actually. As example my rabbitmq service file:

apiVersion: v1
kind: Service
metadata:
  annotations:
    kompose.cmd: kompose convert
    kompose.version: 1.16.0 (0c01309)
  creationTimestamp: null
  labels:
    io.kompose.service: rabbitmq
  name: rabbitmq
spec:
  ports:
  - name: tcp-rabbitmq
    port: 5672
    targetPort: 5672
  selector:
    io.kompose.service: rabbitmq
status:
  loadBalancer: {}

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  annotations:
    kompose.cmd: kompose convert
    kompose.version: 1.16.0 (0c01309)
  creationTimestamp: null
  labels:
    io.kompose.service: rabbitmq
  name: rabbitmq
spec:
  replicas: 1
  strategy: {}
  template:
    metadata:
      creationTimestamp: null
      labels:
        io.kompose.service: rabbitmq
    spec:
      containers:
      - image: rabbitmq:latest
        imagePullPolicy: IfNotPresent
        name: rabbitmq
        ports:
        - containerPort: 5672
        resources: {}
      restartPolicy: Always
status: {}

This config should result in an appearance of rabbitmq as far as I’ve understood. Containerport is exposed as well.

screenshot_jaeger

Jaeger is still showing only one service.

Any idea? Which information am I missing?

Thanks

4

I believe tracing is only supported for http/http2 protocols.

@douglas-reid This probably needs to be added to the naming convention section, as it only mentions “take advantage of Istio’s routing features” - whereas tracing would be a subset of the protocols listed.

5

Correct. Tracing is only supported for http/http2 protocols.

@objectiser sounds right. I’ll file an issue to add to the FAQ.

1 Like