Datadog APM not working

[nanugantiep]

Describe the bug
followed the documentation here to configure datadog but do not see traces coming in from Emissary-Ingress. traces are going fine via datadog agent

To Reproduce
Steps to reproduce the behavior:

1. implement datadog tracing as mentioned here
2. can not see emissary-ingress in datadog APM

Expected behavior
service traces are coming in and see it in Dadadog APM

Versions (please complete the following information):

• Ambassador: emissary:3.9.1
• Kubernetes environment: EKS
• Version: 1.29

Additional context
Configuring Envoy JSON logging in values.yaml via HELM

Tracing service

apiVersion: getambassador.io/v3alpha1
kind: TracingService
metadata:
  name: tracing
  namespace: api-emissary
spec:
  service: "${HOST_IP}:8126"
  driver: datadog
  config:
    service_name: api-ambassador-ingress

Host IP configuration

[danopia]

Hi, I have Datadog APM working with my emissary-ingress, so just taking a guess at what isn't lined up here.

It looks like you are using a non-default AMBASSADOR_ID value. This tends to make emissary-ingress want extra fields in places where the docs don't normally show them. For your TracingService, I do not see the non-default ambassador ID specified anywhere in the YAML. So I would guess that your emissary-ingress thinks that your TracingService does not apply to it.

Perhaps try adding the ambassador_id field like so:

apiVersion: getambassador.io/v3alpha1
kind: TracingService
metadata:
  name: tracing
  namespace: api-emissary
spec:
  service: "${HOST_IP}:8126"
  driver: datadog
  config:
    service_name: api-ambassador-ingress
  ambassador_id:
    - api-ambassador-ingress

Hopefully this helps

[nanugantiep]

@danopia - thank you very much for looking into it. you guessed it right AMBASSADOR_ID is the missing link. i added it to tracing service and ambassador appears in DD APM. once again thank you very much.