Diagnose why our Datadog APM custom spans are not showing up in the service map after migrating our Java Spring Boot application to a new Kubernetes namespace.
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Diagnose why our Datadog APM custom spans are not showing up in the service map after migrating our Java Spring Boot application to a new Kubernetes namespace.
2 real searches · 1 real-search pass
Datadog APM Java custom spans service map not showing custom spans service dependencies Kubernetes namespace trace agent configurationGoogle ↗
OBSERVEDReason
Datadog Java tracer Kubernetes configuration DD_AGENT_HOST DD_TRACE_AGENT_URL service env version unified service taggingGoogle ↗
OBSERVEDInstruction
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT2 real searches · gpt-6
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Datadog APM Java custom spans service map not showing custom spans service dependencies Kubernetes namespace trace agent configuration OBSERVED | Google ↗ AI Mode ↗ | — | Reason | — | — | 1x of 1 | |
Datadog Java tracer Kubernetes configuration DD_AGENT_HOST DD_TRACE_AGENT_URL service env version unified service tagging OBSERVED | Google ↗ AI Mode ↗ | — | Instruction | — | — | 1x of 1 |