The device has completed Telemetry static subscription configuration and the Telemetry sampling path is: huawei-devm:devm/cpulnfos/cpulnfo. If you want to write a script to implement Telemetry…

Question

Options

• Ahuawei-grpc-dialin. Proto
• Bhuawei-devm proto
• Chuawei-telemetry.proto
• Dhuawei-grpc-dialout. Proto

• A
  73% (30)
• B
  27% (11)

Explanation

For gRPC-based Telemetry, three proto files form the required foundation: huawei-grpc-dialin.proto (A) defines the gRPC Dial-In service interface (where the collector connects to the device), huawei-telemetry.proto (C) defines the core telemetry subscription and notification message structures used by both dial modes, and huawei-grpc-dialout.proto (D) defines the Dial-Out service interface for device-initiated data push - which is exactly what "gRPC-based data push" refers to.

Option B (huawei-devm.proto) is incorrect because although the sampling path huawei-devm:devm/cpulnfos/cpulnfo references the DEVM data model, the subscription script treats this path as a plain string identifier - it does not need to import or parse the DEVM data model proto file itself to subscribe or receive the data stream.

Memory tip: Think of it as three layers - transport in (dialin), transport out (dialout), and envelope (telemetry). You need all three layers to send and receive gRPC Telemetry data; the data model proto (huawei-devm) is the content already encoded inside the envelope, so the script doesn't need it directly.

No community discussion yet for this question.