What is data size?

Note: This is applicable only for playbooks that contains rules that uses sensor type as iAgent or SNMP

 

Few playbooks have rules that use sensors of type iAgent (NETCONF) to retrieve data. iAgent sensors can be used when telemetry data is not available.


When any of those playbooks are to be deployed, the size of the RPC response impacts the sizing.
By default it is considered as 100KB as the incoming RPC response size per interval for every iAgent-sensor. In the case of scale scenarios, users are expected to enter this data very carefully by inspecting the XML response they are expected to receiver per interval for the device group.


For Eg:if there are 2 iAgent sensor in a playbook default size is considered as 200KB.
In case of scale environment if the user knows that the xml response is 2MB per interval, please fill the value accordingly in KB.

Healthbot Server Sizing Calculator

This is a tool to calculate the server configuration (vCPUs, RAM and Storage) required to deploy HealthBot for your network/use-case.

Important note:

The server sizing calculation for HealthBot depends on a number of parameters and varies on a case-by-case basis. This tool is a best effort to give you an approximate estimate on the server sizing. The accuracy of the results are highly dependent on the accuracy of your inputs. So please read the example below before you feed the inputs to the HealthBot Server Sizing Calculator.

 

How to use this tool?

Using the tool is very simple. The quick steps are:

  1. Enter the number of devices in a device group.
  2. Select the list of playbooks you would like to deploy on this device group.
  3. Click "-> Add" to add them to sizing chart.
  4. Repeat the above steps for all the device groups you would like to monitor.
  5. Refer to the Sizing Report to see the HealthBot server requirement (approximate estimate) to monitor your network.

Example:

Let’s say you have to monitor a network of 250 devices.

 

Steps to calculate the server sizing for the above requirement:

  1. Enter 100 in the “Number of devices in a device group” text box.
  2. Select playbooks : “system-kpis-playbook” (as system parameters is required to be monitored for all the devices), “bgp-session-stats-playbook” and “bgp-route-hijack-detection”.
  3. Note: When the “system-kpis-playbook” is selected, its data text box gets enabled. Please read the “What is data size” section to understand its importance and how to edit this.

  4. Click “-> Add”.
  5. Enter 50 in the “Number of devices in a device group” text box.
  6. Select playbooks: “system-kpis-playbook” and “Interface-status-playbook”.
  7. Click “-> Add”.
  8. Enter 100 in the “Number of devices in a device group” text box.
  9. Select playbooks: “system-kpis-playbook” and “vpn-view”.
  10. Click “-> Add”.
  11. Sizing Report displays the required server configuration (approximate estimate) in - vCPUs, RAM and Storage. Also displays the number in terms of standard Healthbot servers required.

What is data size?

Note: This is applicable only for playbooks that contain rules that use sensor type as iAgent or SNMP.

 

Few pre-defined playbooks have rules that use sensors of type iAgent  (NETCONF) to retrieve data. iAgent sensors can be used when telemetry data is not available.

When any of those playbooks are to be deployed, the size of the RPC response impacts the sizing.
By default it is considered as 100 KB as the incoming RPC response size per interval for every iAgent sensor. In case of scale scenarios, users are expected to fill this data very carefully by inspecting the XML response they are expected to receiver per interval for the device group.


For example, if there are 2 iAgent sensors in a playbook default size is considered as 200 KB.
In the case of scale environment if the user knows that the xml response is 2 MB per interval, please enter the value accordingly in KB.

 

Sizing Chart:

This section displays the server requirement for every device group for the selected playbooks.

Rules/Fields/Triggers – Shows the consolidated number of fields, rules and triggers from the chosen playbooks. All of these parameters play a crucial role in server sizing.

 

Sizing Report:

This section displays the overall server requirement (approximate estimate) to monitor all the device groups added to the sizing chart.

The left pane displays the consolidated requirement in terms of total number of devices to be monitored, total incoming data in case any iAgent sensors are used and the average number of playbooks per device group in action.

The right pane displays the consolidated server configuration in terms of total number of vCPUs, RAM and storage.

The final requirement is displayed in terms of number of standard servers required to deploy HealthBot.