New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


What placeholders can I use with PRTG?

Votes:

1

Your Vote:

Up

Down

I want to use placeholders (variables) with PRTG when editing Notifications (email, SMS text messages, execute program, etc.), or in the Email Options.

What placeholders are available with PRTG Network Monitor?

help notifications placeholder prtg variables

Created on Feb 3, 2010 10:03:36 AM by  Daniel Zobel [Paessler Support]

Last change on Feb 24, 2011 1:57:20 PM by  Daniel Zobel [Paessler Support]



57 Replies

Accepted Answer

Votes:

4

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 15.4.21 or later

PRTG Placeholders Overview

You can use the listed placeholders (variables) in different settings fields of a notification:

  • Message or Content field of all notifications (where available)
  • Subject field of email and ticket notifications
  • Custom Content field if you choose to send Text with custom content in email notifications
  • Parameter field of Execute Program notifications
  • Postdata field of Execute HTTP Action notifications

Note: Exceptions in usage apply to the the placeholders for Syslogs and SNMP Traps. These can be used in the Custom Content part of Send Email notifications only.

Other Settings

  • For a list of placeholders available in EXE/Script sensor and other custom sensor settings, as well as for command line parameters, please see the More section below.
  • For a list of placeholders available in the Windows Enterprise Console's tools settings, please see the More section below.

Available Placeholders for Email Options and Notifications

Notes about Placeholders:

  • Placeholders are not case sensitive.
  • Placeholders in summarized notifications have limited functionality:
    • The placeholders listed in the following table will not be replaced in the subject field of summarized notifications if there was more than 1 trigger evoked during the summarized time span.
      Exceptions: The placeholders %sitename and %summarycount are always resolved in summarized notifications.
    • If there is only 1 event triggered during the time span you defined, PRTG will not send a summarized notification, but just a normal one. A summarized notification requires at least 2 triggered events.
PlaceholderContainsSynonymVersion/Usage Comment
%colorofstatecolor of the current object status (HTML hex code)might not work in older versions
%companyPaessler's copyright string
%commentsComments entered for the sensor%commentssensorv15.4.21 or later: resolved placeholders contain the heading Sensor Comments
%commentssensorComments entered for the sensor%commentsv15.4.21 or later: resolved placeholders contain the heading Sensor Comments
%commentsdeviceComments entered for the parent devicev15.4.21 or later: resolved placeholders contain the heading Device Comments
%commentsgroupComments entered for the parent groupv15.4.21 or later: resolved placeholders contain the heading Group Comments
%commentsprobeComments entered for the parent probeavailable as of V12.4;
v15.4.21 or later: resolved placeholders contain the heading Probe Comments
%coveragecovered time spanmight not work in older versions
%cumsincesince when data has been accumulated
%dateevent's date, in user's timezone
%datetimeevent's date and time, in user's timezone
%devicename of the device in which the event was triggered%server
%deviceidID number of the device in which the event was triggeredV7.3.2 or later
%downtime the item was down
%downtimeaccumulated downtime
%groupgroup in which the event was triggered
%groupidID number of the group in which the event was triggeredV7.3.2 or later
%historyhistory of sensor events
%homePRTG's web server URL
%hostIP or DNS name of the device that triggered the eventCan be used as Agent IP in SNMP Trap notifications sent by PRTG (V13.x.7 or later)
%iconofstatefilename incl. extension of the icon for the current object statusmight not work in older versions
%lastcheckwhen was the sensor's last scan
%lastdownwhen was the sensor down for the last time
%lastmessagewhat message did the sensor send the last time%message
%lastupwhen was the sensor up for the last time
%lastvaluewhat value did the sensor send the last time
%linkprobethe URL of the probe that triggered the eventmight not work in older versions
%linkgroupthe URL of the group that triggered the eventmight not work in older versions
%linkdevicethe URL of the device that triggered the eventmight not work in older versions
%linksensorthe URL of the sensor that triggered the eventmight not work in older versions
%locationlocation of the device/server for which the event was triggered
%messagewhich message did the sensor send the last time%lastmessage
%namename of the sensor that triggered the event (including sensor type)%sensor
%nodenamename of the node if in a clustermight not work in older versions
%shortnamename of the sensor that triggered the eventV7.1 or later
%priosensor priority setting%priority
%prioritysensor priority setting%prio
%probeprobe under which the event was triggered
%probeidID number of the probe under which the event was triggeredV7.3.2 or later
%programnamePRTG's official name
%programversionPRTG program version
%sensorname of the sensor that triggered the event%name
%sensoridID number of the sensor that triggered the eventV7.3.2 or later
%servername of the device under which the event was triggered%device
%serviceurlService URL configured for the device under which the event was triggeredV9.1 or later
%settingsmiscellaneous sensor settings, such as username for Windows, http, pop3 credentials, etc
%sincesince when the current status is active%statesince
%sitenamePRTG's web server (computer) name
%statesincesince when the current status is active%since
%statuscurrent sensor status
%summarycountreturns the number of events triggered during the defined time spanfor summarized notifications only!
%syslogerrorsmax. last 20 syslog entries before the notification triggerV14.x.10 or later;
works with Syslog Receiver sensors; can be used in the "message" part of Send Email notifications only!
%syslogmessagesmax. last 20 syslog entries before the notification triggerV14.x.12 or later;
works with Syslog Receiver sensors; can be used in the "message" part of Send Email notifications only!
%syslogwarningsmax. last 20 syslog entries before the notification triggerV14.x.10 or later;
works with Syslog Receiver sensors; can be used in the "message" part of Send Email notifications only!
%systemdatetimedate and time when the notification was sent, in user's timezone
%timeevent's time, in user's timezone
%timezoneuser's timezone name
%toaddressaddress to which the notification was sent
%traperrorsmax. last 20 trap entries before the notification triggerV14.x.10 or later;
works with SNMP Trap Receiver sensors; can be used in the "message" part of Send Email notifications only!
%trapmessagesmax. last 20 trap entries before the notification triggerV14.x.12 or later;
works with SNMP Trap Receiver sensors; can be used in the "message" part of Send Email notifications only!
%trapwarningsmax. last 20 trap entries before the notification triggerV14.x.10 or later;
works with SNMP Trap Receiver sensors; can be used in the "message" part of Send Email notifications only!
%uptimeaccumulated uptime

Example (with placeholders):

Date/Time: %datetime

Timezone: %timezone

================================================================

Sensor: %name

Priority: %priority

================================================================

Probe: %probe

Group: %group

Device: %device

Example (placeholders have been replaced):

Date/Time: 11.07.2010 08:57

Timezone: W. Europe Standard Time

================================================================

Sensor: PING 48 (PING)

Priority: 5

================================================================

Probe: Local probe

Group: Paessler Netz

Device: Device 1 [Windows ]

More

  • For a current list of placeholders available in EXE/Script and other custom sensors in your PRTG version, as well as placeholders for command line parameters, please see the API documentation build into your installation: From the web interface's main menu, select Setup | PRTG API, then choose the Custom Sensors tab. For more information, please see How can I use the PRTG Application Programming Interface (API)?
  • For a list of placeholders available in the Windows Enterprise Console's tools settings, please see Enterprise Console: Options—Device Tools

Notes

  • In PRTG versions previous to 15.4.21 you could edit Email Options in the Notification Delivery settings ("System & Website" settings in previous versions). This option has been removed for the ease of use. PRTG uses default content in HTML email notifications as of version 15.4.21. You can still change the content of plain text emails in the email notification settings and also use placeholders here.
  • The placeholder %state is deprecated as of PRTG version 16.x.24. Please use %status instead which has the same functionality.

Created on Feb 3, 2010 10:07:35 AM by  Daniel Zobel [Paessler Support]

Last change on Nov 9, 2016 4:49:14 PM by  Martina Wittmann [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Is there an LOV for the placeholders? Looking for the options for the %message placeholder. Writing rules for another application that PRTG is interfacing to.

Created on Mar 7, 2013 4:41:46 PM by  minigts (0)



Votes:

0

Your Vote:

Up

Down

Dear minigts, %message is ,just as mentioned above, the Message the Sensor returned last. This could be an error Message, Error Code, Message from the used Exe in Case of an exe Sensor and so on. There are no options for the %message Placeholder.

Created on Mar 8, 2013 6:20:28 AM by  Mathias Hengl [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Will it be possible to use these placeholders in sensor settings as well? For example I want to use your "Backup monitoring with PRTG via IMAP" example. I'd be using the same sensor over and over again for many backup checks, so I just want to copy and pase without editing the sensors every time.

So if in the IMAP sensor I could just use %sensor in the "search expression" field it would be ideal. I've had the same thoughts several times with custom sensors as well.

Any chance?

Created on Aug 1, 2014 9:33:07 AM by  Christian Möller (0) 1



Votes:

0

Your Vote:

Up

Down

Dear Christian,

thank you for your feature request.

We understand your need well. However, I'm sorry I have to say 'no' here. The usage of placeholders in sensor settings would evoke too much side effects, so we voted against this feature.

Created on Aug 4, 2014 9:35:23 AM by  Daniel Zobel [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

I don't see a placeholder for Severity. Is there a placeholder for severity?

Created on Apr 8, 2015 2:58:28 PM by  Divyesh Desai (0) 1



Votes:

0

Your Vote:

Up

Down

There is no placeholder for severity sorry. You could look into the %prio placeholder which shows the priority of a sensor, which could work as replacement for severity.

Created on Apr 9, 2015 7:58:33 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Is there a placeholder to show only the sensorname (without the desciption)

When I use de WMIuptimesensor and send an alert when this sensor failed and give this sensor the name "System Up" the description "windows System uptime" can be confusing for some recipients of notifications.

Created on Apr 28, 2015 9:38:28 AM by  compaxo (0) 1



Votes:

0

Your Vote:

Up

Down

Yes, there are two placeholders for a Sensor's Name, below both placeholders with an example representation:

%name: Memory: Physical Memory (SNMP Memory)
%shortname: Memory: Physical Memory


Within PRTG the sensor's name is Memory: Physical Memory and it is an SNMP Memory sensor Type.

Created on Jun 26, 2015 7:11:30 AM by  Luciano Lingnau [Paessler Support]

Last change on Jun 26, 2015 7:11:44 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

how can i use the placeholder "%settings"? I need "%windowspassword" and "%windowsuser" in a "Custom Notification" to start a Powershell Script! But the placeholder are not resolved!?

Created on Jul 20, 2015 8:16:12 AM by  Michel Power (0) 2



Votes:

0

Your Vote:

Up

Down

Do you call them in the parameter field? With single quotes? -UserName '%windowsdomain\%windowsuser' -Password '%windowspassword'

Created on Jul 20, 2015 8:38:30 AM by  Stephan Linke [Paessler Support]

Last change on Jul 20, 2015 10:30:17 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

yes, this is my parameterbox with the placeholders in single quotes in the order of their evaluation:

'%host' '%windowsdomain' '%windowsuser' '%windowspassword' 'emailadress@domain.de'

the placeholder %host' is evaluated, the rest are ignored!?

Created on Jul 20, 2015 9:30:29 AM by  Michel Power (0) 2

Last change on Jul 20, 2015 10:33:14 AM by  Michel Power (0) 2



Votes:

0

Your Vote:

Up

Down

What are you trying to do with the username and password in the notification? Can you post it here?

Created on Jul 20, 2015 10:31:24 AM by  Stephan Linke [Paessler Support]

Last change on Jul 20, 2015 10:31:34 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

When the threshold value of a primary channel of (e.g.: CPU load) sensor has been reached, the PS script use these credentials for the PS-Remote Session, to query some information (e.g.: WMI) and sent this information by email.

Created on Jul 20, 2015 11:06:23 AM by  Michel Power (0) 2



Votes:

0

Your Vote:

Up

Down

Can you try to write the credentials to a text file? Any special characters within the password?

Created on Jul 20, 2015 12:46:54 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

No, this sensor is one of a summary in a library of sonsors and i need this placeholder, because the credentials of the devices are different. The library starts the notification (the ps script including the parameters from above).

Created on Jul 20, 2015 1:21:45 PM by  Michel Power (0) 2



Votes:

0

Your Vote:

Up

Down

It's just about the correct handling of the parameters, not changing the entire notification :)

Created on Jul 20, 2015 1:37:39 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

The same i thought, and i write down a simple ps script, that starts from "custom notification" and parse through all the parameters and send it by email. All i get is the same i write above:

the placeholder %host' is evaluated, the rest are ignored!? (except the emailadress - that is processed correctly) (Article above)

This shows me, the placeholders '%windowsdomain' '%windowsuser' '%windowspassword' are not correctly resolved!

Created on Jul 20, 2015 2:12:15 PM by  Michel Power (0) 2



Votes:

0

Your Vote:

Up

Down

Update Turns out that those placeholders can only be used for custom sensors, not notifications to prevent cross scripting attacks. You can simply use the credential field within the execute program section to execute it as different user. The notification will then be executed in that user context.

Created on Jul 21, 2015 7:19:53 AM by  Stephan Linke [Paessler Support]

Last change on Jul 21, 2015 7:28:28 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I tested it with Adminuser, but the user context you described above, still not use the placeholders (like winuser, -domain, -password)! The same result as above - only "%host" and my emailadress is evaluated.

Please remember, that i've a library with a summary of sensors with different credential to start a custom notification with ps script.(Article)

So, i think there is no way to use this placeholders in Custom Notifications?! No plan to realize it in future versions? IMHO, the placeholder option is safer than to put the single credentials per sensor in clear text parameters, isn't it? ;) But in that way, the custom notification works correctly in my plan - but not in a library - this must use the placeholders :(

Created on Jul 21, 2015 10:08:34 AM by  Michel Power (0) 2



Votes:

0

Your Vote:

Up

Down

The script doesn't get the variables, even if you enter a user. The powershell simply gets executed with a credential object created from the user data. Talked to the dev and it's gonna stay like that :) Maybe this article will help you out :)

Created on Jul 21, 2015 8:03:09 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Would it be possible to add a placeholder for tags? We would like to have the placeholder for HTTP actions.

Created on Jul 21, 2015 8:19:47 PM by  mbrennan (0) 2



Votes:

0

Your Vote:

Up

Down

Would be possible, but this won't happen anytime soon (at least 2-3 month) since it has to be implemented, if it gets considered. Have you tried to use the sensor comments?

Created on Jul 22, 2015 5:25:46 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

^^Thanks for that Link above (Link), but i know that already ;).

So, if i understand correctly, i've to write down for all my sensors in that library a custom notification per Sensor? Is there no other way?

Created on Jul 22, 2015 7:45:15 AM by  Michel Power (0) 2



Votes:

0

Your Vote:

Up

Down

Sorry for the late reply, we had a major outage yesterday and the KB was down.

If you don't want to use the comments to store the variables, yes; then there is no other way around that I'm afraid.

Created on Jul 23, 2015 9:07:59 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

and another positive voice to adding a %tags placeholder. we make extensive use of them in the webinterface so it would be quite handy to show them in alert mails.

Created on Sep 18, 2015 1:10:01 PM by  nickn (0)



Votes:

0

Your Vote:

Up

Down

Consider your voice counted :)

Created on Sep 21, 2015 6:45:24 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Is there any placehoder which contains a unique ID of the alert himself? Not Sensor ID, or Device ID....

Created on Oct 8, 2015 1:33:03 PM by  Oliver (0) 1



Votes:

0

Your Vote:

Up

Down

Alerts do not have IDs in PRTG, so sorry, that is not possible, so there is no such placeholder.

Created on Oct 8, 2015 1:57:21 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Here is another vote for the option to use a placeholder for %tags.

To better explain why, here is my use case: I have different teams in VictorOps (Pagerduty competitor), and my PS script that sends the API call to VictorOps needs a way to route intelligently to different teams via a tag on the sensor. This %tag translates in routing keys that I define in VictorOps... like "Ops_NOC" or "Ops_Network" or "Ops_Devops". These routing keys translate directly to different teams... these teams then have different members with unique schedules and escalation policies, etc. Anyway, I digress.

If you are building PRTG to be able to monitor a ton of different stuff (which you are), you need to provide the ability to alert to different teams programmatically so that one script can have the intelligence to route alerts. As a work around, I am going to have to build one script for each team with routing keys (%tag) hard-coded. This is not best practice.

Thank you for your consideration of this feature request.

-Tim Kidd, Frontline Technologies Group, LLC

Created on Nov 16, 2015 3:24:00 PM by  tkidd (0) 1



Votes:

0

Your Vote:

Up

Down

I myself would like to have two additional placeholders created: %WarningHigh and %WarningLow. In my case I am using this program to monitor Room Temperature and Humidity Sensors located in different Labs. I am forced to use %sensorcomments to show what the threshold value is for both upper and lower warning values and call %sensorcomments out in the email body of text. I do get people who go in and change the warning values but don't change the sensor comments section so it looks pretty stupid when the alarm goes off and the sensor comments says you still within threshold. Hardcoding %WarningHigh and %WarningLow into the email body of text would allow for correct values to be displayed every time.

Created on Jan 26, 2016 4:23:02 PM by  jengel (0) 1



Votes:

0

Your Vote:

Up

Down

Hi iengel, we can put this on the wish list of course. Please be aware though, currently there are no plans to implement further placeholders.

Created on Jan 27, 2016 11:21:04 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Is there a placeholder for sub-groups? It appears there is only a way to have the top level group show in the notification.

Created on Feb 10, 2016 1:58:26 PM by  Will Fox (0) 1



Votes:

0

Your Vote:

Up

Down

Sensors only know their direct parent group as a property. Then they also know their parent Probe. Any group levels between these two are not known to sensors, and are not iterated through for performance reasons, when notifications are triggered. Which is why there are no according placeholders for this.

Created on Feb 11, 2016 8:52:39 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

And another upvote for %tags please add it, because we use tagging extensively. Another placeholder that would be great is %sensorType or %objectType. To contain the information what triggered the Notification (Ping Sensor, Snmp Sensor,...).

Created on Mar 11, 2016 8:52:10 AM by  Fabian Danner (0)



Votes:

0

Your Vote:

Up

Down

another upvote for %tags - this is such a great feature in the Web Frontend and used excessive would be very great to have this also in the notifications

Created on Mar 22, 2016 8:02:41 AM by  ckaufinger (0)



Votes:

0

Your Vote:

Up

Down

I am finding that %probe does not work in the subject of an email. Is there anything I need to do after changing the subject?

Created on Mar 30, 2016 2:44:42 PM by  Mark Underhill (0)



Votes:

0

Your Vote:

Up

Down

Hello Mark, thank you for your post.

I've just tested the functionality of %probe and %probeid and both placeholders were replaced correctly in my test (PRTG Network Monitor 16.1.22.2658). Please note that the behavior may change when using summarized notifications with multiple involved remote probes. You can disable summarization by setting the "Summarization \ Method" to "Always notify ASAP".

Best Regards,

Created on Mar 31, 2016 5:04:54 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello. Please help me to understand what the differences between two placeholders by prtg: "%sensor" and "%name". To send the SMS I use a placeholder "%sensor", but I think that prtg uses the placeholder "%name", because in sms including sensor type, which I do not need. Еxample SMS: "server_room1 220V (SNMP Library) Down". Words (SNMP Library) should be absent when using the placeholder "%sensor". Why it is not?

Created on Apr 7, 2016 1:33:38 PM by  Svetlana Valyiskaya (0)



Votes:

0

Your Vote:

Up

Down

Sventlana, both placeholders deliver the same result, the name of the sensor and the sensor type. I'm afraid this cannot be changed. Sorry.

Created on Apr 8, 2016 1:42:19 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

When using text with custom content option and putting %statesince as a placeholder, the resulting notifications show the value of the %state placeholder plus the word "since" instead of the %statesince value.

I started using the %since placeholder instead, but wanted to give you a heads up.

Created on Apr 13, 2016 4:57:43 PM by  coderoman (0) 1



Votes:

0

Your Vote:

Up

Down

Dear coderoman, I apologize this indeed was a bug. To clear things up, we'll remove the %state placeholder and will only have the %status one.

Created on Apr 15, 2016 7:49:57 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

We REALLY need %tags as a placeholder, so that custom alerts can do "skills based routing" based on Tags.

From the outside, this seems like quite a trivial modification and will have a big impact on the usability of PRTG.

Created on Oct 25, 2016 1:16:24 AM by  mattparkes (0)



Votes:

0

Your Vote:

Up

Down

Currently there are no plans to implement tags as placeholders. Please consider using Comments instead. Comments can be set on group and / or device level as well, and then accessed with placeholders just as well (from higher levels than the sensor just triggering the notification: %commentsdevice. %commentsgroup, %commentsprobe).

Created on Oct 26, 2016 10:14:39 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Torsten,

What if i have a group structure with more than one level of many nested groups ? Do you suggest i place comments on all groups individually ? In complex group designs this could be a major hassle as there's a lot of administrative overhead and a higher chance of making mistakes.

The power of tags is that i can maintain the tags at toplevel and i never have to worry about a childitem not having the tag.

A workaround for me will be to place tags on the toplevel group and to send %deviceid as a parameter to my powershell notification script. My PS script can then do an PRTG API call back to the PRTG server to check if a certain tag is present on the device.

Created on Nov 9, 2016 10:04:32 AM by  Mickael Reijke (0)



Votes:

0

Your Vote:

Up

Down

Dear Mickael

If you have many nested groups, an external solution like your powershell script is currently the best way.

Created on Nov 9, 2016 1:38:11 PM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I'm trying to use the placeholder %comments in my automatic notification. But i wrote in the comment this way: Rua da Quitanda

And at the mensage returned:

Device Comments

Rua da Quitanda

How do i take off this header "Device comments" and get only the "Rua da Quitanda"? Is there any HTML archive i could make some changes?

Created on Dec 23, 2016 12:25:25 PM by  Marlon Andrade (0)

Last change on Dec 23, 2016 1:02:07 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Marlon, we appreciate your contact.

The described behavior is known/expected. There's currently no plan to change this.

Please beware that modifying the content of HTML based notifications is no longer supported as of PRTG's Version 15.4.21.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Dec 23, 2016 1:05:19 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Add my vote for a %tag place holder.

Example use:

We create libraries based on tag filters. With several staff members on different teams using PRTG, some people have assigned tags which can cause duplicate alerts or ticket notifications.

Being able to use %tag allows you to place this within the ticket notification so you can track which tag is associated with the notification.

Created on Jan 24, 2017 12:46:16 PM by  Ted Wagner (0) 2



Votes:

0

Your Vote:

Up

Down

Hi,

Is there a placeholder for the community ?

Thanks

Created on Apr 24, 2017 2:06:14 PM by  reseau_siera (0) 1



Votes:

0

Your Vote:

Up

Down

Hi reseau_siera,

In case you refer to SNMP community string, there is no placeholder for it. Theoretically it can be pulled by PRTG's API, but not in plain text, since it's defined as "credential type" and credentials are only stored encrypted, see also here.

Depending on what you're up to, maybe this might be also of interest to you.

Kind regards,

Erhard

Created on Apr 24, 2017 2:30:17 PM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi, Is there a placeholder for line break ? Thanks

Created on Jun 30, 2017 2:24:05 AM by  Lương Xuân Mạnh (50) 1 1



Votes:

0

Your Vote:

Up

Down

Hi there,

What kind of notification are we talking about? HTTP notifications can use %0A
in their URL which translates into a line break.


Kind regards,
Stephan Linke, Tech Support Team

Created on Jun 30, 2017 10:45:27 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi! How can I use snmp trap body or a part of it for e-mail? And how to get this just for the last trap and not last 20 traps?

Created on Aug 24, 2017 9:13:15 AM by  Vitaliy (0)



Votes:

0

Your Vote:

Up

Down

Hi Vitaliy,

You can only use %trapmessages to retrieve the last 20 messages before the notification was triggered. Other than that, there are no trap related placeholders.


Kind regards,
Stephan Linke, Tech Support Team

Created on Aug 24, 2017 10:12:27 AM by  Stephan Linke [Paessler Support]

Last change on Aug 24, 2017 10:46:13 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks Stephan!

I've almost done it by creating several sensors with a single filter rule. The idea was to have sensors that handle their own kinds of messages and send different alarms. Next I thought PRTG can limit message count that are stored before being purged, but limit is all messages received 2 hours ago... There may be hundreds, thousands messages. I love PRTG because of it's convenience and power, it is a rare kind of production systems that can be used without any manuals reading. And I believe PRTG will continue to power up and give us snmp traps message parcing and other features.

How can I make feature request for this? Thanks!


Vitaliy

Created on Aug 24, 2017 10:32:12 AM by  Vitaliy (0)



Votes:

0

Your Vote:

Up

Down

Unfortunately, the popular demand for this is rather low, hence it probably won't be implemented :( Sorry!


Kind regards
Stephan Linke, Tech Support Team

Created on Aug 24, 2017 3:33:11 PM by  Stephan Linke [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.