DX UIM Sizing Calculator guidance
search cancel

DX UIM Sizing Calculator guidance


Article ID: 277362


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


Is there any available documentation, tips, etc., explaining how to fill in the fields in the UIM sizing tool, for example:

What probes are related to / fall under 'Base Server' monitoring, 'Advanced Monitoring,' etc...

How should we calculate Average QOS for a probe?



  • Currently DX UIM 9.02
  • Sizing tool and guide to be updated for 20.4 CU9 and 23.4 in Jan. 2024


  • The DX UIM sizing tool is a custom tool created by Field Services. Therefore, it was never officially supported but customers may find it quite helpful for estimating UIM environment/UIM database growth.


The Base Server Monitoring section is referring to Systems and Service response monitoring like you would implement with cdm (CPU, Memory and DIsk), processes (process monitoring), ntevl, ntservices, etc.

Systems and Service Response Monitoring

The Advanced Server Monitoring section might include any type of server monitoring that is not considered 'basic' such as WebSphere, Apache, Tomcat, etc.. 

Network Monitoring would include network device monitoring, snmpcollector, snmptd, net_connect, Cisco monitoring, etc.

Network Infrastructure Monitoring

'Line up' the rest of the probe categories that you can find at the url shown below with the UIM Sizing Tool section: "Specify what you want to monitor"

DX Unified Infrastructure Management Probes - Monitoring

Set the Data Retention and Aggregation values according to the data_engine settings for each type of data/table, RN (raw), HN (Historical), BN (baseline) etc.

Normally, you should leave the 'Control Values' as is.

The 'System Requirements' link currently produces a 404, but this is the working link and proper page that should be displayed:

Prepare Your Server Hardware

Additional Information

--These queries are similar and count the detailed # of qos. This first query listed below should help with understanding the average # of qos per source/probe. 

select probe,de.name, source, COUNT(distinct target)'numtarget'

 from s_qos_definition de with(nolock), s_qos_data da with(nolock), cm_configuration_item_metric co with(nolock), cm_configuration_item it with(nolock), cm_device dv with(nolock)

 where de.qos_def_id = da.qos_def_id

  and co.ci_id = it.ci_id

 and it.dev_id = dv.dev_id

 group by probe, de.name

, source order by probe, de.name,source


select de.name, de.description , origin, robot, source, target , probe,  de.unit_short, de.r_table, de.h_table, samplerate, table_id,da.ci_metric_id

 from s_qos_definition de with (NOLOCK), s_qos_data da with (NOLOCK), cm_configuration_item_metric co with (NOLOCK), cm_configuration_item it with (NOLOCK), cm_device dv  with (NOLOCK)

where de.qos_def_id = da.qos_def_id

  and co.ci_id = it.ci_id

 and it.dev_id = dv.dev_id

 group by table_id,de.name, de.description , origin, robot, source, target , probe,  de.unit_short, de.r_table, de.h_table, samplerate,da.ci_metric_id order by de.name