PRTG Manual: Cisco Meraki License Sensor

The Cisco Meraki License sensor monitors Meraki licenses of an organization via the Cisco Meraki Dashboard API.

Cisco Meraki License Sensor

Cisco Meraki License Sensor

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

  • Dutch: Cisco Meraki Licentie
  • French: Cisco Meraki licence
  • German: Cisco Meraki Lizenz
  • Japanese: Cisco Meraki ライセンス
  • Portuguese: Licença da Cisco Meraki
  • Russian: Лицензия Cisco Meraki
  • Simplified Chinese: Cisco Meraki 许可证
  • Spanish: Licencia Cisco Meraki

Remarks

Consider the following remarks and requirements for this sensor:

Remark

Description

Enabled organization API access

This sensor requires that you enable the access of an organization to the Cisco Meraki Dashboard API.

i_round_blueIf the API access for an organization is disabled, you must enable it manually. For more information, see Cisco Meraki Dashboard API: Enable API Access.

API key

This sensor requires an API key with Cisco Meraki Dashboard API permissions.

i_round_redThe API key that this sensor uses must inherit the permissions of a Cisco Meraki Dashboard Administrator account with at least Read-only admin permissions.

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

Credentials

This sensor requires credentials for Cisco Meraki.

IPv6

This sensor supports IPv6.

Performance impact

This sensor has a very low performance impact.

Limits

This sensor has predefined limits for several metrics.

Scanning interval

  • The minimum scanning interval of this sensor is 10 seconds.
  • The recommended scanning interval of this sensor is 6 hours.

Multi-platform probe

You can add this sensor to a multi-platform probe.

Basic Sensor Settings

Basic Sensor Settings

Basic Sensor Settings

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

  • cisco
  • license
  • meraki

i_square_cyanFor more information about basic sensor settings, see section Sensor Settings.

Cisco Meraki Specific

Cisco Meraki Specific

Cisco Meraki Specific

Setting

Description

Organization

The name of the organization that the monitored licenses belong to.

Sensor Display

Sensor Display

Sensor Display

Setting

Description

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel below the sensor's name. The available options depend on what channels are available for this sensor.

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

Graph Type

Define how this sensor shows different channels:

  • 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.
    i_round_redYou 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 select Stack channels on top of each other above.

Select a unit from the list. PRTG stacks all channels with this unit 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.

Debug Options

Debug Options

Debug Options

Setting

Description

Result Handling

Define what PRTG does with the sensor result:

  • Discard result (default): 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.

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

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

Inherited Settings

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 b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Channel List

i_round_blueWhich channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.

Channel

Description

Days to Expiration

The days to expiration

i_round_blueThis channel is the primary channel by default.

i_round_blueThis channel has default limits:

  • Lower error limit: 30 days
  • Lower warning limit: 90 days

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

License Count

The number of licenses

License Model

The license model of the monitored license

  • Up status: Co-Termination, Per-Device
  • Warning status: Unknown

More

i_square_blueKNOWLEDGE BASE

What security features does PRTG include?