dt-obs-network-devices

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Network Devices Skill

网络设备Skill

Analyze SNMP-monitored network infrastructure in Dynatrace — switches, routers, firewalls, load balancers, access points, and any other device polled by a network device extension (the SNMP-generic and vendor SNMP extensions). This skill covers the device and interface data model and routes each question to the right reference file. All DQL lives in the reference files and was validated against a live tenant with
dtctl query
.
在Dynatrace中分析由SNMP监控的网络基础设施——交换机、路由器、防火墙、负载均衡器、接入点以及任何由网络设备扩展(通用SNMP扩展和厂商专属SNMP扩展)轮询的设备。本Skill涵盖设备与接口数据模型,并将每个问题引导至对应的参考文件。所有DQL语句均存储在参考文件中,且已通过
dtctl query
在真实租户环境中验证。

What Network Device Monitoring Tells You

网络设备监控能为你提供什么信息

SNMP extensions poll network hardware and expose it in Dynatrace as three layers:
  • Topology — an inventory of devices and their interfaces as Smartscape nodes (
    EXT_NETWORK_DEVICE
    ,
    EXT_NETWORK_INTERFACE
    ), with attributes (vendor, model, OS/firmware, location, contact, IPs, MACs, link speed) and relationships (which interface belongs to which device; which devices are neighbors via LLDP/CDP).
  • Metrics — time series for device health (CPU, memory, uptime) and per-interface health (operational/admin status, in/out throughput, errors, discards, packet mix), under the
    com.dynatrace.extension.network_device.*
    namespace.
  • Logs — event-driven records: SNMP traps (link-up/down, hardware faults), syslog messages (config changes, authentication, interface events), and auto-discovery activity (devices and neighbors found per poll cycle).
This answers questions such as: Which interfaces are down? Which links are saturated? Is this router's CPU pegged? Which devices rebooted? What is connected to this switch? What traps has this device sent? What syslog errors are recurring?
SNMP扩展会轮询网络硬件,并在Dynatrace中以三层数据的形式展示:
  • 拓扑层——设备及其接口的清单,以Smartscape节点(
    EXT_NETWORK_DEVICE
    EXT_NETWORK_INTERFACE
    )呈现,包含属性(厂商、型号、操作系统/固件、位置、联系人、IP、MAC、链路速度)和关系(接口所属设备;通过LLDP/CDP发现的邻居设备)。
  • 指标层——设备健康状态(CPU、内存、运行时间)和单接口健康状态(运行/管理状态、入/出吞吐量、错误、丢弃、数据包类型占比)的时间序列数据,位于
    com.dynatrace.extension.network_device.*
    命名空间下。
  • 日志层——事件驱动型记录:SNMP陷阱(链路通断、硬件故障)、系统日志(配置变更、认证、接口事件)以及自动发现活动(每个轮询周期发现的设备和邻居)。
这可以解答如下问题:哪些接口已故障?哪些链路已饱和?该路由器的CPU是否满载?哪些设备已重启?该交换机连接了哪些设备?该设备发送过哪些陷阱?哪些系统日志错误重复出现?

The Three Layers (and how they join)

三层数据(及其关联方式)

LayerQuery withGrainKey fields
Topology
smartscapeNodes "EXT_NETWORK_DEVICE"
/
smartscapeNodes "EXT_NETWORK_INTERFACE"
One row per device / interface (current inventory)
id
,
name
,
monitoring_mode
,
device_type
,
location
,
ip
,
speed
, edges via
belongs_to
/
calls
Metrics
timeseries … com.dynatrace.extension.network_device.*
Time series per device / interfacegrouped by
dt.smartscape.ext_network_device
and (interface metrics)
dt.smartscape.ext_network_interface
Logs
fetch logs | filter dt.openpipeline.source == "…"
Individual log records (traps, syslog, discovery)joined to topology by expanding the device
ip[]
array and matching
device.address
/
dt.ingest.source.ip
— see references/logs.md
The join key is the Smartscape ID. Every metric carries a
dt.smartscape.ext_network_device
dimension (and interface metrics also carry
dt.smartscape.ext_network_interface
). Use
lookup [smartscapeNodes …]
to attach human-readable device/interface names to metric results, and to attach live metrics to an inventory listing. Both reference files show this pattern.
层级查询方式粒度关键字段
拓扑层
smartscapeNodes "EXT_NETWORK_DEVICE"
/
smartscapeNodes "EXT_NETWORK_INTERFACE"
每个设备/接口对应一行(当前清单)
id
name
monitoring_mode
device_type
location
ip
speed
,通过
belongs_to
/
calls
关联的边
指标层
timeseries … com.dynatrace.extension.network_device.*
每个设备/接口对应一条时间序列
dt.smartscape.ext_network_device
分组(接口指标还需按
dt.smartscape.ext_network_interface
分组)
日志层
fetch logs | filter dt.openpipeline.source == "…"
单个日志记录(陷阱、系统日志、发现记录)通过展开设备
ip[]
数组并匹配
device.address
/
dt.ingest.source.ip
与拓扑层关联——详见references/logs.md
关联键为Smartscape ID。每个指标都带有
dt.smartscape.ext_network_device
维度(接口指标还带有
dt.smartscape.ext_network_interface
维度)。使用
lookup [smartscapeNodes …]
可将易读的设备/接口名称附加到指标结果中,或将实时指标附加到设备清单中。两个参考文件均展示了该模式。

Monitoring Mode Determines What Data Exists

监控模式决定可用数据

Every device has a
monitoring_mode
. This is the first thing to check — it decides whether metrics exist at all:
monitoring_mode
MeaningHas metrics?Has full attributes?
Extension
Directly polled by an SNMP extensionYes — full
com.dynatrace.extension.network_device.*
set
Yes
Discovery
Discovered on the network but not directly polledNoPartial
Neighbor
Known only because a polled device names it as an LLDP/CDP neighborNoMinimal (name, chassis MAC)
If a device has no metrics, check its
monitoring_mode
before assuming a data gap — only
Extension
-mode devices are polled. When listing "monitored devices," exclude
Neighbor
(and usually
Discovery
).
每个设备都有
monitoring_mode
属性。这是首先需要检查的内容——它决定了是否存在指标数据:
monitoring_mode
含义是否有指标?是否有完整属性?
Extension
由SNMP扩展直接轮询——完整的
com.dynatrace.extension.network_device.*
指标集
Discovery
在网络中被发现但未被直接轮询部分属性
Neighbor
仅因被轮询设备通过LLDP/CDP列为邻居而被识别最小属性(名称、机箱MAC)
如果设备没有指标数据,请先检查其
monitoring_mode
,不要直接认为存在数据缺口——只有
Extension
模式的设备会被轮询。在列出“已监控设备”时,需排除
Neighbor
(通常也排除
Discovery
)模式的设备。

Routing

问题路由

  1. Inventory, attributes, or topology (list devices, find a device's interfaces, map neighbors, read model/firmware/location) → references/topology-model.md.
  2. Health or performance (CPU, memory, uptime, interface up/down, throughput, saturation, errors) → references/metrics.md.
  3. Event-driven signals (SNMP traps, syslog messages, discovery activity) → references/logs.md.
  4. Most real questions combine layers (e.g. "which interfaces on the core router are down" = metric status filtered to one device, joined to interface names). The metrics and logs references show these joined queries.
  1. 清单、属性或拓扑(列出设备、查找设备的接口、绘制邻居关系、查看型号/固件/位置)→ references/topology-model.md
  2. 健康或性能(CPU、内存、运行时间、接口通断、吞吐量、饱和度、错误)→ references/metrics.md
  3. 事件驱动信号(SNMP陷阱、系统日志消息、发现活动)→ references/logs.md
  4. 大多数实际问题会涉及多个层级(例如*“核心路由器上哪些接口已故障”* = 过滤到单个设备的指标状态,关联接口名称)。指标和日志参考文件展示了这些关联查询。

Related Skills

相关Skill

Network device monitoring is one part of Dynatrace network observability. Route elsewhere when the question is not about device/interface health or topology:
The user wants…Use
Traffic between entities, top talkers, conversations, connection health (the flows through the network)dt-obs-network-flows — including NetFlow/IPFIX/sFlow that these same devices export
Host NIC throughput / packet drops on OneAgent-monitored hosts (not SNMP devices)dt-obs-hosts
references/host-metrics.md
Service request rate, latency, error ratedt-obs-services
Setting up or configuring an extension (this skill covers the resulting data model, not extension authoring)dt-obs-extensions
General Smartscape traversal syntax (
traverse
,
smartscapeEdges
,
references[…]
)
dt-dql-essentials
Network devices vs. network flows. This skill answers "what is the state of the box and its ports" (SNMP device/interface health and topology).
dt-obs-network-flows
answers "what traffic is crossing the network" (conversations, bytes, talkers). The same router appears in both: here as an
EXT_NETWORK_DEVICE
with interface counters, there as a NetFlow exporter. A future macro
dt-obs-network
skill may unify them; until then, cross-link.
网络设备监控是Dynatrace网络可观测性的一部分。如果问题与设备/接口健康或拓扑无关,请引导至其他Skill:
用户需求…使用…
实体间的流量、热门会话方、会话、连接健康(流经网络的流量)dt-obs-network-flows ——包括这些设备导出的NetFlow/IPFIX/sFlow
由OneAgent监控的主机上的NIC吞吐量/数据包丢弃(非SNMP设备)dt-obs-hosts
references/host-metrics.md
服务请求速率、延迟、错误率dt-obs-services
扩展的设置或配置(本Skill涵盖生成的数据模型,不涉及扩展开发)dt-obs-extensions
通用Smartscape遍历语法(
traverse
smartscapeEdges
references[…]
dt-dql-essentials
网络设备与网络流的区别。本Skill解答*“设备及其端口的状态如何”(SNMP设备/接口健康和拓扑)。
dt-obs-network-flows
解答
“哪些流量正在通过网络”*(会话、字节数、会话方)。同一路由器会出现在两者中:在此处它是带有接口计数器的
EXT_NETWORK_DEVICE
,在网络流Skill中它是NetFlow导出器。未来可能会有一个**
dt-obs-network
**宏Skill将两者统一;在此之前,请交叉引用。

Reference Files

参考文件

  • references/topology-model.mdValidated. The Smartscape model:
    EXT_NETWORK_DEVICE
    and
    EXT_NETWORK_INTERFACE
    node types with full field reference, monitoring modes, and the
    belongs_to
    /
    calls
    edges. DQL for device inventory (with filtering by mode/type/location/vendor), listing a device's interfaces, resolving an interface to its device, and mapping device/interface neighbor topology.
  • references/metrics.mdValidated. The
    com.dynatrace.extension.network_device.*
    metric catalog with units, dimensions, and field-typing rules. DQL for device health (top CPU, memory % with fallback, uptime and reboot detection) and interface health (down interfaces, throughput and saturation vs. link speed, error/discard counts, per-device interface detail), each joined to device/interface names.
  • references/logs.mdValidated. The three log sources: SNMP traps (
    extension:com.dynatrace.extension.snmp-traps-generic
    ), syslog (
    extension:syslog
    ), and auto-discovery activity (
    extension:com.dynatrace.extension.snmp-auto-discovery
    ). Covers the IP-to-Smartscape join pattern (
    device.address
    /
    dt.ingest.source.ip
    snmp.ip
    ), field references for all three sources, and DQL for recent traps with device names, trap frequency by OID, error syslog, top event patterns, combined per-device view, and LLDP/CDP neighbor discovery logs.
  • references/topology-model.md —— 已验证。Smartscape模型:
    EXT_NETWORK_DEVICE
    EXT_NETWORK_INTERFACE
    节点类型的完整字段参考、监控模式,以及
    belongs_to
    /
    calls
    边。用于设备清单(按模式/类型/位置/厂商过滤)、列出设备接口、将接口关联到设备、绘制设备/接口邻居拓扑的DQL语句。
  • references/metrics.md —— 已验证
    com.dynatrace.extension.network_device.*
    指标目录,包含单位、维度和字段类型规则。用于设备健康(CPU使用率TopN、内存占比及 fallback、运行时间和重启检测)和接口健康(故障接口、吞吐量和饱和度与链路速度对比、错误/丢弃计数、单设备接口详情)的DQL语句,每个语句均关联了设备/接口名称。
  • references/logs.md —— 已验证。三种日志源:SNMP陷阱(
    extension:com.dynatrace.extension.snmp-traps-generic
    )、系统日志(
    extension:syslog
    )和自动发现活动(
    extension:com.dynatrace.extension.snmp-auto-discovery
    )。涵盖了IP到Smartscape的关联模式(
    device.address
    /
    dt.ingest.source.ip
    snmp.ip
    )、所有三种源的字段参考,以及用于查询带设备名称的近期陷阱、按OID统计陷阱频率、错误系统日志、Top事件模式、单设备综合视图、LLDP/CDP邻居发现日志的DQL语句。