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

Core Server x Remote Probe x User Preview

Votes:

0

Hi,

we are testing the product and we have the following need:

- We need a single management console to centralize all the visualization of the infrastructure that will be monitored, of each client. This console needs to be Web.

- Each end customer should have their individual access and should see only their dashboard and their devices being monitored.

So, we understand that it would work like this:

- We will install a core server - We will install 30 remote probes (in each infrastructure of our customer);

However, we note that the remote probes limit is 30 per core server.

So, would we have to install a new core server? Will the access to the web portal for these other clients (above 30) be different from the first ones (30 clients)?

Explaining the scenario:

- Server Core 1 (https://portal1.company.com.br) - 30 remote probes

- Server Core 2 (https://portal2.company.com.br - 30 remote probes

If this is the product architecture scenario, is there any way for both the (Serve Core1 and Server Core 2), have a single web portal and that we can manage the access to users to see, only the information of their devices?

If we have part of the devices of a client on the different core servers, will I be able to free the view of the unified devices?

Expected Scenario:

- Web Portal Central: (https://portal.company.com.br) - Server Core 1 (Manage up to 30 remote probes) - Server Core 2 (Manage up to 30 remote probes) - Server Core 3 (Manage up to 30 remote probes) ....on...

Thank you.

prtg snmp wmi

Created on Nov 16, 2017 7:56:44 PM



3 Replies

Votes:

0

Hi there,

The 30 probes is not a hard limit defined by us, it is more a guideline. The "limit" depends more on the amount of sensors per probe. May I ask you how much devices/sensors you are planning to monitor?

By the way, if you want extensive support, you can surely contact our Pre-Sales team which will help you further and more extensively.

Best regards.

Created on Nov 17, 2017 12:30:10 PM by Dariusz Gorka [Paessler Support]



Votes:

0

Hello,

our scenario is well distributed, but the items we monitor are the basics.

Our concern is in case of need to add another server core, we understand that the new users serve core, need to access another web address and also, but information will be in another database. This is bad because we will have two different data sources.

From the calculations that we have made, we will need a scenario with 3500 sensors, distributed in 30 remote probes. Using the average you mention on the site.

Monitor basically: CPU, DISK, MEMORY, SERVICE, NETWORK and PING.

The larger remote probes we would need, should monitor on average some 20 servers and some networking devices.

In our datacenter, where the core server will be installed, we have a heavy activity, which is monitoring all the data links of these 30 clients.

That is, we will monitor data link 130, with sensors (ping, packtloss, and traffic bandwidth)

Most are small with one or two devices.

I will illustrate:

- Client A - Servers: 20 - Networking Devices: 3 - Web pages: 2 - Backup email: 1

- Client B - Servers: 10 - Networking Devices: 3 - Web pages: 1 - Backup email: 1

- Client C - Servers: 41 - Networking Devices: 25 - Web pages: 1 - Database: 5 (Oracle, SQL) - Backup email: 1

- Client D - Servers: 1 - Network Devices: 1 - Web pages: 0 - Backup email: 1

- Client E - Servers: 1 - Network Devices: 1 - Web pages: 0 - Backup email: 1

Tks.

Created on Nov 17, 2017 12:52:01 PM



Votes:

0

Hi there,

Unfortunately, that is not really a good topic for the Knowledgebase, as suggested, please contact our Pre-Sales Team as they will help you further with the planning of your PRTG installation. You can reach them under [email protected].

Best regards.

Created on Nov 17, 2017 1:29:24 PM by Dariusz Gorka [Paessler Support]




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.