PRTG Manual: Cisco Meraki Network Health Sensor
The Cisco Meraki Network Health sensor monitors the health of Cisco Meraki network devices via the Cisco Meraki Dashboard API.
This sensor is in beta status. The operating methods and the available settings are still subject to change. Do not expect that all functions work properly, or that this sensor works as expected at all.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Cisco Meraki Network Health
- French: Cisco Meraki – État du réseau
- German: Cisco Meraki Netzwerkzustand
- Japanese: Cisco Meraki ネットワークの正常性
- Portuguese: Cisco Meraki Network Health
- Russian: Работоспособность сети Cisco Meraki
- Simplified Chinese: Cisco Meraki 网络运行情况
- Spanish: Salud de la red Cisco Meraki
- This sensor requires that the Beta Sensors experimental feature is enabled.
- This sensor requires that the access of an organization to the Cisco Meraki Dashboard API is enabled.
- This sensor requires credentials for Cisco Meraki in settings that are higher in the object hierarchy.
- This sensor supports IPv6.
- This sensor has a very low performance impact.
Requirement |
Description |
---|---|
This sensor requires that the Beta Sensors experimental feature of PRTG is enabled.
|
|
Cisco Meraki sensors require that the access of an organization to the Cisco Meraki Dashboard API is enabled. If the API access for an organization is disabled, you must enable it manually. For more information, see Cisco Meraki Dashboard API: Enable API Access.
|
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.
|
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe.
|
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority ( |
Setting |
Description |
---|---|
Network |
The name of the network that this sensor monitors. |
Organization |
The name of the organization that the monitored network belongs to. |
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
Setting |
Description |
---|---|
Result Handling |
Define what PRTG does with the sensor result:
|
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
The minimum scanning interval of this sensor is 10 seconds.
The recommended scanning interval of this sensor is 5 minutes.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
For more information, see section Root Group Settings, section Channel Unit Configuration.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status |
IOT "Alerting" |
IOT devices in alerting status |
IOT "Dormant" |
IOT devices in dormant status |
IOT "Offline" |
IOT devices in offline status |
IOT "Online" |
IOT devices in online status |
MR "Alerting" |
Meraki Radios (MR) devices in alerting status |
MR "Dormant" |
MR devices in dormant status |
MR "Offline" |
MR devices in offline status |
MR "Online" |
MR devices in online status |
MS "Alerting" |
Meraki Switching (MS) devices in alerting status |
MS "Dormant" |
MS devices in dormant status |
MS "Offline" |
MS devices in offline status |
MS "Online" |
MS devices in online status |
MX "Alerting" |
Meraki Security (MX) devices in alerting status |
MX "Dormant" |
MX devices in dormant status |
MX "Offline" |
MX devices in offline status |
MX "Online" |
MX devices in online status |
Uplinks "Active" |
Uplinks in active status
|
Uplinks "Failed" |
Uplinks in failed status |
Uplinks "Not Connected" |
Uplinks in not connected status |
Uplinks "Ready" |
Uplinks in ready status |
KNOWLEDGE BASE
What are beta sensors and how can I use them?
What security features does PRTG include?