When a tunnel is created in prtg an ID is automatically generated, is there a way to change it?

Modified on 2025-06-10 14:53:05 +0200

Every time I make a tunnel an ID is automatically created, for example "(5846523)Company", every time this tunnel falls and when it comes back the ID changes automatically and the monitoring does not recognize this new ID created and keeps showing the old one, ie , every time a tunnel falls when the ID changes but the old one is not changed and I can't monitor the new automatically, I would have to configure the new one precisely because of the ID, would be able to disable the ID or leave it fixed?

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hi,

This behavior is correct as the tunnel has a new ID which PRTG could not identify. If you run an auto discovery after the tunnel has received the new ID, PRTG will create a new sensor for this tunnel. So please make sure that the ID does not change or create a new sensor every time a tunnel gets a new ID.

Sep, 2021 - Permalink

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.

When a tunnel is created in prtg an ID is automatically generated, is there a way to change it?

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.