- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Device profiles define which metrics to collect and how to transform them into Datadog metrics. Each profile is expected to monitor a class of similar devices from the same vendor.
The Device Onboarding Experience provides a guided, GUI-based experience to:
For more information on advanced profile details, review the Profile Format Reference page.
The minimum Agent version required is 7.50 or higher.
The profile home page is where you can see a snapshot of the device profiles you created using the Device Onboarding Experience.
SysObjectID. This is what is used to match network devices to the device profiles that define what is collected and monitored from each device.Add global tags for more advanced and granular options, which allows you to assign a weight to a specific metric.
| Modification | Description |
|---|---|
| No Modification | The device’s returned value will be used directly as the tag value. |
| Format | This can be mac_address or ip_address. |
| Extract Value | A regular expression used to extract the tag value from the SNMP value provided by the device. |
| Mapping | This is described here. |
Adding tags to tabular metrics is similar to adding global tags, with two additional options:
Select whether the tag value originates from an OID value or a segment of the table index. If Index is chosen as the source, an index position must be specified, which then becomes the tag.
Consider a table at OID 1.2.3.1.1 with two indices. Each row in this table includes a two-number index. Suppose column 3 of a row has OID 1.2.3.1.1.3.55.12 - here, 1.2.3.1.1 represents the table, .3 is the column number within the table, and .55.12 is the index of this specific row (all other columns for this row will also end with .55.12). If you establish a tag with the Source set to Index and Index Position set to 1, the tag’s value for metrics from this table row will be 55; if you set the index position to 2, it will be 12. If you use an index less than 1 or more than the number of indices in the table, the tag will not be populated.
See Using an Index for more information.
Use Index Transformation when you need to tag a table metric value with a value from a different table that employs a subset of this table’s index. This is not a typical scenario. You configure this by adding one or more transformation segments, each with a start and end number. These numbers index into the original table’s index to create a new index value for the new table.
Consider the CPI-UNITY-MIB module. It has a table, cpiPduTable, with details about a specific PDU, and another table, cpiPduBranchTable, with information about specific PDU branches. The index of the main table is the PDU’s MAC address, such as 6.0.36.155.53.3.246. The branch table’s index is a branch ID followed by the PDU MAC, therefore a branch table row index might be 1.6.0.36.155.53.3.246.
If you want to report the current on a PDU branch, you could add cpiPduBranchCurrent (OID 1.3.6.1.4.1.30932.1.10.1.3.110.1.3, from the branch table) as a tabular metric. To tag this metric with the PDU name, add cpiPduName as a tag (OID 1.3.6.1.4.1.30932.1.10.1.2.10.1.3, from the main table), then add an index transform with start:1 and end:7. This means the branch current metric from the branch table indexed with 1.6.0.36.155.53.3.246 would be tagged using the name from the main table indexed with 6.0.36.155.53.3.246.
For more information see Using a column from a different table with different indexes.
The advanced options for scalar and tabular metrics are the same:
gauge, rate, monotonic_count, or monotonic_count_and_rate..zip bundle which contains the yaml files for the profiles you created.yaml files in the profile directory on each of the relevant installed Agents.
| |
