Link Collection Troubleshooting Guide¶
Before trying to troubleshoot the problem of link data collection, you need to understand the transmission path of link data. The following is a schematic diagram of link data transmission:
graph TB
sdk[Language problem / SDK] --> workload[Workload cluster otel collector]
--> otel[Global cluster otel collector]
--> jaeger[Global cluster jaeger collector]
--> es[Elasticsearch cluster]
classDef plain fill:#ddd,stroke:#fff,stroke-width:1px,color:#000;
classDef k8s fill: #326ce5, stroke: #fff, stroke-width: 1px, color: #fff;
classDef cluster fill:#fff,stroke:#bbb,stroke-width:1px,color:#326ce5;
class sdk,workload,otel,jaeger,es cluster
As shown in the figure above, if the transmission fails at any step, the link data cannot be queried. If you find no link data after applying Link Boost, follow these steps:
-
Use the DCE 5.0 platform, enter
Observability
, and selectDashboard
in the left navigation bar. -
Click on the dashboard title
Overview
. -
Switch to
insight-system
->insight tracing debug
dashboard. -
You can see that the dashboard consists of three blocks, which are responsible for monitoring the data status of different clusters and transmission links of different components. Through the generated timing chart, check whether there is any problem with the data transmission of the link.
-workload opentelemetry collector -global opentelemetry collector -global jaeger collector
Block introduction¶
-
workload opentelemetry collector
It shows that
opentelemetry collector
of different working clusters is receiving language probe/SDK link data and sending aggregated link data. You can select the cluster you are in through theCluster
selection box in the upper left corner.Note
According to these four timing diagrams, it can be judged whether the
opentelemetry collector
of the cluster is running normally. -
global opentelemetry collector
It shows how
opentelemetry collector
ofglobal service cluster
receives link data fromotel collector
inworking cluster
and sends aggregated link data.Note
The
opentelemetry collector
of theglobal management cluster
is also responsible for sending the audit log and Kubernetes audit logs (not collected by default) to theaudit server
component of the global management module. For example, you can check whether this function is normal through the timing diagram in the lower right corner. -
global jaeger collector
Show that
jaeger collector
ofglobal management cluster
is receiving data fromotel collector
inglobal management cluster
, and sending link data to ElasticSearch cluster.