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

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Downtime problems - additional channel

Votes:

0

Your Vote:

Up

Down

I have used jmeter to check web page availability. I wrapped it in wsh script. PRTG is executing that script and gets number of errors in format: 0:OK or count:Error (for example 1:Error)

I have configured PRTG as follows:

  • Sensor type: EXE/Script
  • Primary channel:"bledy"
  • Value type: integer
  • Unit string: szt
  • Channels: Downtime ID:-4 bledy ID:0
  • Channel Downtime configuration is default
  • Channel bledy is configured to have enabled limits and all limits are set to "0" - zero.

And in result:

  • Sensor is changing its state between red/green according to number of errors reported by jmeter.
  • When sensor is red (in error state when there are any errors reported by jmeter) but downtime (in Live data or Historical Data report) is set only sometimes.

How to promote error state to Downtime?

Or how to report downtime when sensor goes to any number different than "0"?

To show how strangely PRTG behaves I paste "Live data" from that sensor: As You can see the "1" value not always triggers downtime condition.

Date Time 	bledy	Downtime	Coverage 
2010-05-11 15:45:20	0 szt	0 %	100 %
2010-05-11 15:44:14	0 szt	0 %	100 %
2010-05-11 15:43:15	0 szt	0 %	100 %
2010-05-11 15:42:14	0 szt	0 %	100 %
2010-05-11 15:41:13	0 szt	0 %	100 %
2010-05-11 15:40:25	1 szt	100 %	100 %
2010-05-11 15:39:21	1 szt	100 %	100 %
2010-05-11 15:38:21	1 szt	0 %	100 %
2010-05-11 15:37:13	0 szt	0 %	100 %
2010-05-11 15:36:13	0 szt	0 %	100 %
2010-05-11 15:35:19	0 szt	0 %	100 %
2010-05-11 15:34:20	1 szt	0 %	100 %
2010-05-11 15:33:13	0 szt	0 %	100 %
2010-05-11 15:32:14	0 szt	0 %	100 %
2010-05-11 15:31:20	1 szt	0 %	100 %
2010-05-11 15:30:17	0 szt	0 %	100 %
2010-05-11 15:29:15	0 szt	0 %	100 %
2010-05-11 15:28:20	1 szt	0 %	100 %
2010-05-11 15:27:13	0 szt	0 %	100 %

I am using: PRTG Network Monitor 7.2.4.5051

channels custom-sensor downtime prtg

Created on May 11, 2010 1:50:36 PM by  lsczygiel (0) 1

Last change on Mar 12, 2012 12:36:27 PM by  Daniel Zobel [Product Manager]



1 Reply

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hello,

We only consider a downtime if there are at least two following downs. Because only then we have a definite downtime. Everything else is merely an educated guess.

This is the mentioned 'downtime problem', that a single down is not accounted as downtime. The difference is, that downs caused by an error-limit need literally two scanning intervals, whereas a 'normal' down gets an immediate re-scan, and might appear as red marked in the live-table also when it went down for one scanning interval only.

Best Regards.

Created on May 13, 2010 9:07:56 AM by  Torsten Lindner [Paessler Support]

Last change on May 26, 2010 1:44:53 PM by  Daniel Zobel [Product Manager]



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.