<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Cisco Meraki Network Health Sensor

Enabled Beta Sensors experimental feature

This sensor requires that the Beta Sensors experimental feature of PRTG is enabled.

For more information, see the Knowledge Base: What are beta sensors and how can I use them?

Enabled organization API access

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.

The API key inherits the permissions of the Cisco Meraki Dashboard Administrator account that was used to generate the API key.

Network

Select the networks that you want to monitor. PRTG creates one sensor for each network that you select.

Enable check boxes in front of the respective lines to select the items. Use the check box in the table header to select all items or to cancel the selection. In large tables, use the search function in the upper-right corner.

Sensor Name

Enter a name to identify the sensor.

Parent Tags

Shows tags that the sensor inherits from its parent device, parent group, and parent probe.

This setting is for your information only. You cannot change it.

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.

It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

For performance reasons, it can take some minutes until you can filter for new tags that you added.

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

• cisco
• meraki

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 () to the highest priority ().

Network

Shows the name of the network that this sensor monitors.

PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

Organization

Shows the name of the organization that the monitored network belongs to.

PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

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.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

• Show channels independently (default): Show a graph for each channel.
• Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you enable Stack channels on top of each other as Graph Type. 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.

Result Handling

Define what PRTG does with the sensor result:

• Discard result: Do not store the sensor result.

• Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.

This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

In a cluster, PRTG stores the result in the PRTG data directory of the master node.

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 in percent.

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

This channel is the primary channel by default.

Uplinks "Failed"

Uplinks in failed status

Uplinks "Not Connected"

Uplinks in not connected status

Uplinks "Ready"

Uplinks in ready status