- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Supported OS
This integration provides comprehensive visibility into your Cisco Meraki Environment by collecting metrics for Network Device Monitoring, Network Event Logs, and Security Event Logs for Cloud SIEM.
Network Device Monitoring
Network Device Monitoring helps ensure the overall health of network infrastructure is up to standard by identifying potential bottlenecks and device configuration errors.
This integration collects metrics for the following devices:
This integration dynamically pulls in device tags and metadata from Meraki environments to easily drill down into specific device groups, locations, or device types.
Security Event Logs
Security Event Logs alert on events such as intrusion detections, firewall rule violations, and malware threat detections to helps identify and respond to potential security threats.
Create your own rules or leverage the out-of-the-box Cloud SIEM rules for real-time threat detection and incident response.
Network Event Logs
Network Event Logs help network administrators analyze historical network events and troubleshoot issues efficiently.
These logs track the following topics:
In addition to the recommended monitors included with this integration, additional monitors can be configured to notify administrators of critical events, allowing for proactive network management.
To collect metrics from your Meraki Cloud Controller, configure the SNMP integration with the Meraki Profile.
To configure collection of NDM Metrics, an API key is required from Meraki.
Device Tag Filters allow you to specify which devices to monitor within NDM. You can specify multiple tags by separating them with a comma. If no tags are specified, all devices will be monitored.
To configure collection of network event logs and security event logs, an API key is required from Meraki.
For more information, see the Cisco Meraki Dashboard API.
Switch level port metrics for port traffic and usage are not available.
Configure the SNMP integration with the Meraki Profile to collect metrics (prefixed snmp.
in the following table) from your Meraki devices. Alternatively, create a custom profile to collect additional metrics. Note that metrics prefixed meraki.
are collected via the Datadog Meraki integration, enabled using the preceding instructions.
meraki.avgLatencyMs (gauge) | The average network latency in Milliseconds. Shown as millisecond |
meraki.clientCount (count) | The client count per network. Shown as unit |
meraki.devStatus (count) | The status of the device. Shown as unit |
meraki.latencyMs (gauge) | The latency of an uplink in Millseconds. This is only supported for MX devices. Shown as millisecond |
meraki.lossPercent (gauge) | The loss percent of an uplink in a network. This is only supported for MX devices. Shown as percent |
meraki.powerModuleStatus (count) | The power module status of a device. Shown as unit |
meraki.uplinkStatus (count) | The status of an uplink on a device. This is only for MX, MG, Z series devices in the org. Shown as unit |
meraki.utilization (count) | The channel utilization of an AP in a network. Shown as unit |
meraki.utilization.non_wifi (count) | The non wifi channel utilization of an AP in a network. Shown as unit |
meraki.utilization.wifi (count) | The wifi channel utilization of an AP in a network. Shown as unit |
meraki.port.status (count) | The status of a port on a Meraki switch. Shown as unit |
meraki.devPerformanceScore (gauge) | The device performance score. Shown as unit |
snmp.devStatus (gauge) | The status of the device's connection to the Meraki Cloud Controller Shown as unit |
snmp.devClientCount (gauge) | The number of clients currently associated with the device Shown as unit |
snmp.devInterfaceSentPkts (gauge) | The number of packets sent on this interface Shown as packet |
snmp.devInterfaceRecvPkts (gauge) | The number of packets received on this interface Shown as packet |
snmp.devInterfaceSentBytes (gauge) | The number of bytes sent on this interface Shown as byte |
snmp.devInterfaceRecvBytes (gauge) | The number of bytes received on this interface Shown as byte |
meraki.interface.sent (gauge) | The number of bytes sent for each uplink of a network. Shown as byte |
meraki.interface.received (gauge) | The number of bytes received for each uplink of a network. Shown as byte |
meraki.vpn.receivedInKb (gauge) | The number of kilobytes received for each uplink of a network. Shown as kilobyte |
meraki.vpn.sentInKb (gauge) | The number of kilobytes sent for each uplink of a network. Shown as kilobyte |
meraki.vpn.avgLossPercentage (gauge) | The average loss percentage of an uplink in a network. Shown as percent |
meraki.vpn.minLossPercentage (gauge) | The minimum loss percentage of an uplink in a network. Shown as percent |
meraki.vpn.maxLossPercentage (gauge) | The maximum loss percentage of an uplink in a network. Shown as percent |
meraki.vpn.avgJitter (gauge) | The average jitter of an uplink in a network. Shown as unit |
meraki.vpn.minJitter (gauge) | The minimum jitter of an uplink in a network. Shown as unit |
meraki.vpn.maxJitter (gauge) | The maximum jitter of an uplink in a network. Shown as unit |
meraki.vpn.avgMos (gauge) | The average mos of an uplink in a network. Shown as unit |
meraki.vpn.minMos (gauge) | The minimum mos of an uplink in a network. Shown as unit |
meraki.vpn.maxMos (gauge) | The maximum mos of an uplink in a network. Shown as unit |
meraki.vpn.status (count) | The status of the VPN. Shown as unit |
meraki.vpn.avgLatencyMs (gauge) | The average VPN network latency in Milliseconds. Shown as millisecond |
meraki.vpn.maxLatencyMs (gauge) | The maximum VPN network latency in Milliseconds. Shown as millisecond |
meraki.vpn.minLatencyMs (gauge) | The minimum VPN network latency in Milliseconds. Shown as millisecond |
The Meraki integration does not include any events.
The Meraki integration does not include any service checks.
Datadog sometimes encounters issues accessing Meraki from its servers. Add Datadog’s IPs to your IP address allow list to ensure that crawling works as expected.
Need help? Contact Datadog support.
Additional helpful documentation, links, and articles: