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


HTTP content reported unexpected format

Votes:

0

Your Vote:

Up

Down

Hi,

I recently use a HTTP content sensor to check file copy time. The script is : $time=Measure-Command -Expression {Copy-Item sourcepath destpath -Recurse -Force -Confirm:$False} write-host "<html>" write-host "<body>" "["+ $time.Totalminutes +"]" write-host "</body>" write-host "</html>"

and this command is been output into an empty html with right format like [2.1313131] that said by PRTG document like bellowing, For example, consider a URL http://www.example.com/status.html that returns a PHP script with the current system status in a simple HTML page as follows:

<html>
<body>
 Description: Script gives back current status of disk free (%) and CPU usage (%).
 [85.5][12.0]
</body>
</html>

However, it reported as the unexpected format when I using the http content sensor with 1 channel and float setting.

Does someone could help me on this?

http-content-sensor script sensor unexpected-format

Created on Sep 8, 2015 2:02:57 AM by  kelvin_xue (0) 1



2 Replies

Votes:

0

Your Vote:

Up

Down

So the script runs independently and just writes the content to the status.html file, correct? When I put the finished HTML code into a site and point the HTTP Content sensor to it, it'll work just fine.

Could you possibly be a bit more detailed about the structure of the script/html thingy? :)

Created on Sep 9, 2015 5:44:01 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Stephan,

I found the root cause due to I have to redirect the output as ASCII rather than UNICODE. This issue already been fixed .

Thanks

Appreciated

Created on Sep 10, 2015 2:24:14 AM by  kelvin_xue (0) 1



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.