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.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

How can i log access to 5050/5051

Votes:

0

Your Vote:

Up

Down

User Story

I use the HTTPPush-Sensors to post results and data from scripts to a prtg probe. Currently I have to add a sensor manually to receive data. I have found no way to automate that or find out, what a client uses which token.

Details of User Story

I have two use cases to have a more dynamic creation of sensors based on HTTPPush-Requests 1. PowerShel Scripts on Servers who do local checks (some kind of agent) and post the results to prtg. they are dynamic and generate a url like "https://prtg:5051/secret-computername-scriptname=content=....". It would be great to generate a ticket in PRTG for a "pending sensor", if this token is not already defined. It could be similar to the process to appove a new probe.

2. i use some IoT Devices (ESP8266 etc) and they generate a random key during the first start and store them in their flash. All messages are sent to PRTG using http://prtg:5050/uniquekey?content=... These devices do not have a gui display or anything else. So i use wireshark to capture these and collect the keys.

3. I found no logging somewhere about access to these service handler in the "Logs" directory of the probe. PRTG is logging a lot of stuff (webserver, sensors, core, probe). Logging requet to 5050/5051 or other probeports offering a HTT/REST-API is necessary to detect errors and abuse.

Acceptance criteria

- First step: Please add a logging of requests on the probe. I could use that to parse the logs and tell me about request with a "Matching sensor :0" results and solve that on the server and not check the clients

- future step: Add a ticket or approval process to create a HTTPushSensor from a request t a undefined token.

Status

Open

add-feature httppush logging

Created on Aug 28, 2020 2:35:03 PM by  Frank Carius (341) 1 1



Replies

Nobody has replied yet

Why not be the first?

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.