<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Tags

For every object in your PRTG setup, you cannot only name objects, but also define tags in the object settings to additionally mark an object as a member of certain categories. Although there are tags predefined when adding objects, you are completely free in the way you add tags. For example, you can mark all of the bandwidth sensors which are especially important for you with the tag bandwidth_important.

Later, you can view lists of objects with certain tags (helpful for multi-edit of settings), or choose sensors by tag when creating reports. A clever arrangement of tags can save you a lot of time at some point. Press one of the keys enter, space, or comma to confirm a tag.

Note: You can also change tags for several objects at a time using the multi-edit function.

View and Edit Tags in Basic Sensor Settings 

View and Edit Tags in Basic Sensor Settings 

Tags Are Inherited

The tags in the settings of an object are automatically inherited by all other objects underneath in the Object Hierarchy. You can view inherited tags in section Parent Tags in the settings of a sensor, device, or group. So, for example, a device with the tag myExampleTag automatically passes on this tag to all sensors which you create on it. These sensors appear in lists then whenever you search for myExampleTag. This is useful, for example, when you add sensors by tag in reports settings.

This way, to configure your setup for fetching all sensors on a device by tag, you do not have to tag every single sensor, but it is enough to tag the device. Inheritance for tags cannot be disabled.

Filtering with Tags

You can use tags to filter table lists for specific objects, or to add sensors to Libraries and Reports. For example, you can show only sensors on the sensors overview page which have the tag bandwidth_important. You can also use more than one tag to filter for monitoring objects like sensors.

When filtering with tags, you can also use plus (+) and minus (–) signs in front of tags to categorize them:

  • Tags with + must exist for an object to be shown
  • Tags with – must not exist for an object to be shown
  • At least one tag of the tags without + or – must exist for an object

The filter shows an object only if all three conditions are true. The order of the tags in a tag field does not matter.

For example, if you enter –windows into a tag field, all sensors/devices that do not have "windows" as tag are shown. With +windows or windows you filter for objects which are tagged with "windows".

You can use more than one logical operator in a tag field: For example, if you enter +netflow –bandwidth_important into a tag field, the corresponding list, library, or report includes all sensors that are tagged with "netflow" but not with the tag "bandwidth_important". If you enter netflow bandwidth_important, a sensor has to be tagged with "netflow" or "bandwidth_sensor" or both to be affected.

 

 

Keywords: Tags