Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Storage Manager (STM) > SRM Profiler Administrator Guide > Add VMware monitoring > SRM Profiler and vCenter asset collection

SRM Profiler and vCenter asset collection

Table of contents
No headers

Updated: June 16, 2017

Customers with very large virtual environments might encounter an issue where asset data is not being reported for virtual devices. This issue can be caused by timeout issues due to an influx of too much data to SRM Profiler. SRM Profiler versions 6.0 and above have resolved this issue by adding a feature allowing customers to throttle the amount of data being polled by SRM Profiler. The new feature can be seen when clicking the "Show Advanced Fields" button in the device configuration window for the virtual device. The fields are:

  • Number of Connection to VC for Asset
  • Number of connection to VC for Storage
  • Number of connection to VC for Performance

    File:Success_Center/Reusable_content_-_InfoDev/SRM_Profiler/Storage_Manager_and_vCenter_Asset_Collection/0200005E_319x369.jpg

The default settings is 3 yet customers can adjust the values to fit their environment. You can also modify the time for when Configuration, Performance, Storage and Discovery Frequency is collected thus avoiding any scheduled overlap with data collection from the virtual device.

    File:Success_Center/Reusable_content_-_InfoDev/SRM_Profiler/Storage_Manager_and_vCenter_Asset_Collection/0200005F_298x345.jpg

When you set the values and click Save, the changes are automatically cascaded to any additional proxy agents that are monitoring ESX servers associated with the vCenter, thus saving you time from having to manually duplicate the settings for each proxy agent.

 
Last modified

Tags

Classifications

Public