What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

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

Auto-Discovery creates ALL AWS CloudWatch sensors



When running Auto-Discovery on a subnet, PRTG is creating ALL AWS CloudWatch sensors for EVERY device it finds.

For example, it will create 180 AWS CloudWatch sensors - sensors for EVERY AWS instance we have, and it will do this for EVERY device found during the Auto-Discovery. So, if we're deploying a tier of 20 new devices (servers) for our dev subnet, it will create approx 180 sensors x 20 servers = 3600 sensors. The interesting point, none of these newly found devices are in fact AWS instances, they're all in our VMware. It makes for a tedious cleanup each time.

How do I prevent PRTG from auto-discovering AWS CloudWatch sensors on non-AWS devices?

amazon-cloudwatch-sensor auto-discovery aws

Created on Aug 24, 2018 3:11:30 PM

2 Replies

Accepted Answer



Hello there,
we appreciate your contact.

The behavior you've described will take place if you've entered the AWS Credentials (key and secret) at the root, probe or at group level.

Whenever a discovery runs on a device, it will create Cloudwatch sensors when it "is able to". Basically, there is no restriction in PRTG about on where AWS sensors need to be created (because enforcing this would make things very static), so we've decided that there should be no limitation about where these sensors can be deployed.

To avoid these unwanted sensors, simply enter the Cloudwatch credentials only on the device were you will deploy the AWS sensors and not anywhere else. This way the standard auto-discovery will not be able to create these sensors on every device.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Aug 27, 2018 12:09:06 PM by  Luciano Lingnau [Paessler]



Following up, this has worked as we'd like. Thanks.

Created on Nov 5, 2018 6:44:33 PM

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.