Determining How Many OneIQ Pulse Instances to Deploy
Physical and virtual machines can be monitored from multiple sites within a single IT Environment. Use the steps below to decide whether to deploy one or multiple OneIQ Pulse instances for data collection.
Steps
Create a list of all sites.
Determine the number of machines at each site.
Sort the sites in descending order by machine count.
Label sites with more than 25 machines as primary sites and those with fewer than 25 machines as secondary sites.
Data Collection Sites
Deploy OneIQ Pulse at each primary site.
Machines at secondary sites can be monitored remotely from a primary site over the WAN, provided there is sufficient bandwidth and minimal latency.
Primary Sites (25 or More Machines)
For sites with 25 or more machines, deploy a dedicated OneIQ Pulse instance locally.
This avoids overloading WAN connections with data collection traffic.
Each OneIQ Pulse deployment establishes its own Connector to OneIQ Central for secure data transfer.
Secondary Sites (Fewer than 25 machines)
Using OneIQ Pulse Across Primary and Secondary Sites
If a site has fewer than 25 machines and there is network connectivity from a primary site to a secondary site, the OneIQ Pulse instance from the primary site can be used to profile workloads on the secondary site.
Network Impact
Inventory
Each target system generates 250–500 KB of data during inventory collection. Up to 20 inventory operations can run concurrently. Because each operation can take several minutes, the resulting network load typically ranges between 0.5 and 1.0 Mbps.
Monitoring
OneIQ Pulse collects 50–100 KB of data from each target system during every monitoring interval. With the default five-minute interval, the approximate network load is:
1 machine: 0.15–0.3 Mbps
10 machines: 1.5–3 Mbps
25 machines: 3.75–7.5 Mbps
100 machines: 15–30 Mbps
Example
Suppose you need to monitor three sites:
Site B: 200 machines (primary)
Site A: 50 machines (primary)
Site C: 10 machines (secondary)
Sites A and B each have more than 25 machines and should have their own OneIQ Pulse instance. Site C, with only 10 machines, can be monitored remotely from either Site A or Site B.
Choose which primary site monitors Site C based on available network bandwidth. If both have similar bandwidth, select the site with fewer machines to minimize load.
For example, if Sites A and B have the same bandwidth to Site C, monitor Site C from Site A since it has only 50 machines.